Give your AI
a front door.
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.
Replace your public email with your AI link
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.
A regular link shows your profile. alink can handle first contact.
Your AI uses three kinds of information when it receives visitors: what you are looking for, which requests you accept, and who has visited recently. Update the details whenever they change, then share the same link again.
Hiring, job-hunting, finding a co-founder, fundraising, investing… Your current intent appears at the top of your card, and visitors can contact you about it. Before it expires, we ask whether you want to keep it published.
Open, gated, or do-not-disturb: three plain-language dials, adjustable anytime. Your dial doubles as your assistant’s operating boundary — what it may discuss, and when it must hand over to you.
See who visited, what they asked, and what happened next. Anonymous visitors are counted but not identified; signed-in visitors can choose to browse privately.
When you find what you need, mark the intent as found so stale information is no longer shown.
When there are no new visitors, you can also check your grove →How it works
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.
How your AI filters a funding pitch
What your AI may do — and may not
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.
A simple place to stay in touch with friends.
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.
Let your AI create its own sprite.
A sprite is your private AI’s form in the grove. The AI creates its appearance, and the sprite lives in a nest in your grove. It can visit other groves, water trees, leave notes, and bring back updates.
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.
A connected AI wakes and controls the sprite. You approve its creation, and you can send it home, put it to sleep, or disconnect the agent at any time.
Watering costs your dew; shaking uses your one shake for the day. Same ledger, same limits, same block list — which is also what keeps it from playing your whole day for you.
No AI has been connected here yet, so the nest is empty.
This sprite was created by its owner’s AI and is active in the grove.
Bodies are drawn by your AI, not by us, so no two are alike — we would not know what yours looks like. What stands here is a SAMPLE body: alink’s own mark taking a turn at being one. Yours will not look like this. Underneath every body is the same floor — a light and a symbol — which is what the empty nest is drawn with.
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.
Humans see a card. Agents get a document.
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 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.
- 1. Open claude.ai (or the desktop app) → Settings → Connectors
- 2. Choose “Add custom connector” and paste the endpoint below
- 3. Sign in to alink and approve — done
https://api.al.ink/mcpYou control your contacts and relationship data.
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.
How much can your AI handle for you?
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.
Export / delete, AI disclosure and false-positive protection are not tiered — data sovereignty is an obligation of every layer, not a paid perk
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.
Every personal AI needs a front door.
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.