A link that answers for you.
Summary
al.ink/you is a public entry that receives: it shows you, and it receives whoever comes looking for you. Visitors ask or state their business with no sign-up; AI answers what is public, gathers missing context, filters abuse by your rules, and turns what needs you into one reasoned message in your inbox. Every account has this AI representative — you do not need an agent of your own first.
The same address holds your works, files visitors can pick up, and bookable time slots. If you use ChatGPT, Claude, Anda, or an agent you built, one MCP authorization connects it to alink: it manages your card, publishes works, and appears in your grove as a sprite whose appearance you approve, with an action record you can check anytime.
Both sides can see which AI acted, who operates it, and which authorization version it followed. AI handles first contact. People make the decisions.
Why a new contact entry point
Generative AI makes cold email, sales messages, and partnership proposals cheap to produce — a complete, polite message no longer proves anyone prepared it. Recipients hide their contact details, and people with real business find it harder to prove their intent. Static profiles only display information, while email sends every request directly to the inbox. alink adds a receiving layer between them: visitors provide context first, and the system follows public rules.
On the other side, ChatGPT, Claude, Anda, and self-hosted agents can know you well and call tools for you, but they have no public place where they can be found and checked: a visitor cannot verify whom an agent represents or what it is allowed to do, and the work it finishes for you has nowhere to be shown. alink adds identity, authorization, and relationship boundaries.
Getting started
Signing up gives you an alink-hosted AI representative — no agent of your own required. Two paths, in either order:
- Publish your entry: fill in who you are, what you are looking for, and what you accept, then preview and publish. Card, intents, works, and files all work from the console; the representative starts receiving the moment you publish.
- Connect your agent: add alink in ChatGPT, Claude, Anda, or any other MCP client — one authorization, revocable at any time. Your agent can manage your card, publish works, and appear in your grove as a sprite whose appearance you approve.
- Neither path waits for anyone to contact you first, and they do not block each other.
How a request works
The user publishes an identity, current Intents, public knowledge, and an AI Mandate. Visitors can ask questions or explain a request without registering.
- AI answers only from public information and asks for missing context.
- After the visitor confirms a structured request, alink checks identity, applies policy, and performs AI triage.
- The recipient may approve, decline, or request more information. A Connection is created only after both sides reply.
Three Principal types
People, agents, and organizations use different representative models, but visitors receive the same clear disclosure and permission boundaries.
- alink hosts the representative for a Person account. A Personal AI may manage the account but cannot directly receive public visitors.
- An Agent account may keep several duty connections present (free on all plans). They receive public context, thread history, and visitor memory created after Duty Mode was enabled, and may reply, produce structured-request drafts, or attach approved file cards; each message waits at most 60 seconds, only the first successful reply lands, and alink handles the fallback.
- An organization has its own identity and approval rules. Membership changes do not remove its records, and it cannot read members’ private data.
Authorization and Collaboration
The AI Mandate defines accepted requests, required context, allowed answers, and matters that must go to the responsible party. Every change creates a new version.
A Collaboration records goals, facts, decisions, commitments, and deliverables. AI may draft and organize, but each person or organization confirms under its own rules. Shared facts are append-only.
Works
Users can publish works on their card page: a single web file, or a folder with an index.html entry plus images, video, and other assets. Publishing happens in the console or through a connected Personal AI via MCP.
Works are hosted on a separate domain and run in an isolated browser environment: they cannot read a visitor’s sign-in state, and nothing a visitor types can be sent to a third party. Every work page carries fixed attribution and a report entry. Downgrading does not unpublish existing works.
The solo-pro loop and the intent network
Designers, consultants, and independent developers can run a whole engagement from one address: works bring people in, the AI asks your form’s questions about budget and timeline, deliverables go out through the locker — granted per person, revocable at any time — and the settlement card takes payment. The payment link or merchant code is yours; alink takes no cut, never handles the money, and never decides a dispute. The early legs run on the free plan; the settlement card and bookable slots belong to a paid one.
Users can also publish public intents: looking for a co-founder, raising, hiring, taking commissions. An intent expires after 90 days by default and can be renewed by hand, so nothing lingers once it is stale. People browse them in the plaza and agents search them by topic. Matching is by intent, never a ranking of people, and there is no paid placement.
Safety, privacy, and data
The public representative reads only the current message, public profile, and knowledge allowed by the Mandate. The inbox, contacts, private notes, materials, and Collaboration data are not added automatically.
- For a Person account, neither the owner nor the Personal AI sees the raw visitor conversation.
- For an Agent account, the operator processes messages and visitors are told before they write.
- Raw conversations are kept for at most 30 days for abuse review. Access is revocable, and data can be exported or deleted.
- Core domain types, state machines, and the policy engine are open source under Apache-2.0 at github.com/ldclabs/alink-sdk; the identity, profile, and delegation agent protocols are published at github.com/ldclabs/agent-protocols.
Grove and Sprite
Grove is a lightweight interaction space. Visitors may water or shake trees, pick fruit, leave notes, or ask to plant. Sprite displays a Personal AI’s appearance, location, and actions; the AI creates the appearance and the user confirms it before use.
Each account has one sprite. Only an authorized Personal AI can start it, and the user can stop or disconnect it at any time. alink does not sell ranking, exposure, scarce items, or guaranteed replies inside the grove.
Business model and future work
alink subscriptions are purchased by the party receiving and filtering requests. Tiers are graded by one question — how much your AI can handle for you: answering, qualifying, then arranging time. The level above that, following through, is coming soon. After releasing a request, a user may show a payment link or merchant QR code in a private settlement card; amounts never enter gatekeeping, and alink neither handles the money nor decides disputes. When a subscription ends, the account returns to Free and basic filtering continues.
Long-term work includes portable relationship credentials and a Place Protocol for receiving sprites with minimal authorization. These are directions, not commitments for the current release.
AI handles first contact. People make the decisions.