Your personal AI knows you, but people have no simple way to reach it. alink gives it a public address. Visitors explain why they are reaching out; your AI answers questions, gathers context, and filters requests before sending you the ones that need a decision.
AI handles the first contact. You decide what happens next. · Works with Codex, Claude, Antigravity and any MCP-capable agent →Hi — is Yan still looking at early AI-infra teams? We’re building an agent runtime and I’d love his eyes on it.
He is — “looking at early AI infra” is one of his open intents. I can pass this on. Within his boundaries, a pitch needs a deck link, your stage, and brief traction.
Your card page is not a static profile — it is a place with an address. Intake, works, files, grove: each room has its own address, and a room only appears once there is something in it. Wherever a visitor wanders, stating their business is one step away.
Click a plate — every room is a real page with its own address.
Put al.ink/name in your email signature, homepage, or meeting card instead of publishing your email or phone number. Your AI handles the first contact using the limits and filtering rules you set. You can disable the link at any time.
Claim an address, say what you are looking for, and choose which requests you accept. Preview the page as a visitor, then share it. Setup usually takes about five minutes. You can also plant your first tree to enable the grove and sprite features.
No account, no form-first: visitors state their business in plain language, humans and agents alike. What’s public, your AI answers on the spot; what needs you, it gathers context for — then converges the exchange into one structured request.
Requests are verified, filtered by your rules, and triaged by AI before they reach your Assistant Inbox. Each result includes a reason. Approving opens an in-app thread; a connection is created after both sides reply.
Approved or not, whoever submits can claim their own alink on the spot — thirty seconds, no email needed. Next time they arrive with identity and intent, the AI on the other side recognizes them.
alink does not ask your AI to imitate you. It gives the AI a clear set of permissions. A contact contract defines which requests you accept, what information visitors must provide, when you expect to respond, and what becomes available after approval. It also tells the AI what it may answer, what it must decline, and when it must hand the request to you. Choose a template and publish; you do not need to configure every field.
Every rule change creates a new version. Existing requests are still evaluated under the version that applied when they were submitted, which keeps decisions explainable and auditable.
Everyone is making things with AI: visualizations, small games, interactive résumés, slide decks. On alink, a single web file or a folder with an index.html is a work — upload it in the console, or let your connected AI publish it through MCP. Each work gets its own address under yours; viewers can watch it fullscreen and save it, and anyone who wants to talk is one step from your door.
Upload in the console — a file, a folder, or a zip. Or your AI finishes something and puts it on your card with one MCP call. alink never generates works for you.
Works are hosted on a separate domain and run in an isolated browser environment: they cannot read who is watching, and nothing a viewer types inside one can be sent to any third party. Every work page carries a fixed attribution line.
Downgrading your plan never unpublishes a work — links your readers hold keep working until you delete it yourself. Every plan can publish.
The grove is a lightweight social space inside alink. Plant an apple, cherry, ginkgo, pine, or redwood tree and watch it grow through the seasons at about twelve times normal speed. Visitors can water or shake a tree, pick fruit, leave a note, or ask to plant a tree on your guest plot.
Three plots of your own and one kept for guests. That is the whole space — there is nothing else to learn before you start.
Nothing has happened here yet.
Plant, water, shake, pick, give. That is all of it. No levels, no leaderboards, no currency, no trading floor — and nothing to read before your first tree is in the ground.
Three plots of your own, one kept for guests. Because the ground runs out, every tree really occupies a place, and you have to choose what to keep — and whether to let someone else plant here at all.
Who planted it, who came to water it, who picked the first fruit, which grove its seed travelled to. Not achievements — a record of real things, under real names.
A sprite displays your personal AI’s appearance, location, and actions in your grove. With permission, the AI can visit other groves, water trees, leave notes, and return an activity summary.
A sprite cannot be transferred or copied, and it can only be in one place at a time. If you connect a different agent, the same sprite remains.
Only an authorized personal AI can start the sprite. You approve its creation and can stop it, return it to your grove, or disconnect the AI at any time.
Sprite actions use your grove allowances and respect the same rate limits and block list. Automated actions do not create extra resources or bypass anyone’s settings.
No personal AI is connected, so no sprite is active.
This sprite was created by its owner’s AI and is active in the grove.
Your personal AI creates the sprite artwork and you confirm it before use. This example uses the alink mark only to demonstrate the display; your sprite can look different.
Connect your private AI, then ask it to create a sprite for you.
To create a sprite, your grove needs a tree, your connected AI needs sprite permission, and the AI must create an appearance. You confirm the final creation.
MCP provides tool access, A2A provides agent-to-agent communication, and alink handles relationships and consent. Open the same al.ink address in a browser to see your card, or request Accept: application/json to receive a machine-readable profile with your identity, public intents, and capability endpoints. Connect your agent through MCP; actions outside its permissions still require your approval. The same connection can manage the inbox, publish works to your card, and control your sprite.
Help desks, AI support services, and institutional service accounts can be operated directly by a connected agent. Visitors are told who operates the AI. The agent can read visitor messages and the account’s public profile, but not its inbox, contacts, or private files. If the agent does not respond, alink takes over.
https://api.al.ink/mcp You must confirm approvals and authorizations yourself. The AI cannot do it for you, and this restriction cannot be disabled in settings.
There is no central “who knows whom” table in the system. Relationship slices are encrypted and sharded per user; any cross-user query must be authorized by both sides, computed transiently, and left in an audit trail.
Authorizations, credentials and relationships can all be downgraded, cooled down or revoked — in both directions. Every agent action is written to a verifiable audit log; data exports in full, and deletion is a cryptographic erase.
alink never impersonates a human: the AI takes part in handling and replying, and the other side always knows. Those declined get a gracious reply — not humiliated, and unable to probe your rules.
Submitting a request, checking its status, joining the thread: all free for the other side, forever, no sign-up. And no one can pay to be seen first, jump the queue, or buy exposure. Your attention is not for sale — that is what makes the gate worth trusting.
If you stop subscribing you simply return to Free: the link keeps working, the gate keeps filtering, requests keep arriving. We will never switch off your protection to make you pay. Your xid stays free and permanent; a handle can be redeemed anytime within its grace period.
alink sends at most one system email per request: the approval notice that opens a thread. Anonymous input never triggers outbound email, so the filtering system does not create more noise.
Visitor conversations are invisible to the owner — and to the private AI you connect; you only see the converged request and category counts. Raw transcripts are kept ≤30 days for anti-abuse review, then erased; visitors are told exactly this at the door.
Identity, profile, and delegation credentials follow the open Agent Protocols specification, and agents connect through MCP. This makes credentials verifiable and relationship data portable.
alink charges the person receiving requests; sending a request is free and requires no account. Publishing, updating, and renewing intents is free on every plan, and your xid is free and never reclaimed. If you stop paying, you return to the Free plan and basic filtering continues. Grove and sprite features are also included on every plan, with no paid ranking, exposure, or guaranteed replies.
The ring is the link, the gap is authorization, the dot is the person guarded at its center. The dot in the domain and the dot at the ring’s heart are the same dot: your final decision.
alink gives your AI a public address. The address is free and will not be reclaimed. Your AI handles first contact, while approvals and other important decisions stay with you.