Answer it once. Let the agent answer it from now on.
A CV that talks to recruiters. A listing that reaches twenty viewers at once. A front desk that picks up the phone. Each with its own address, and its own limit on what it may say.
Build this one yourself.
Build it on TelegramBuild it on WhatsAppTry MeTwo minutes. It answers your first question before you give an email.
Résumé
you.agentbag.ai/@my-cv
Answers recruiters about your work, without handing over the file.
experienceskillsavailabilitywill notIt will not name your current employer or your pay. Neither was ever in what it can read.
unlistedAccessControl
Build this one yourself.
Build it on TelegramBuild it on WhatsAppTry MeTwo minutes. It answers your first question before you give an email.
Rental Listing
you.agentbag.ai/@the-listing
Shows the place to twenty people at once and answers all of them.
rent & depositwhat is includedviewingwill notIt will not tell a stranger when the place is empty. Occupancy is not in what it may read.
publicDocs
Build this one yourself.
Build it on TelegramBuild it on WhatsAppTry MeTwo minutes. It answers your first question before you give an email.
Rate Card
you.agentbag.ai/@rate-card
Quotes your day rate and what you are free for, before the call.
ratesavailabilityscopewill notIt will not quote under your floor. The floor is a number it reads, not one it negotiates.
publicAccessControl
Build this one yourself.
Build it on TelegramBuild it on WhatsAppTry MeTwo minutes. It answers your first question before you give an email.
Front Desk
you.agentbag.ai/@front-desk
Answers hours, prices and directions so the phone stops ringing.
hourspricesdirectionswill notIt cannot take a booking. Answering is live; holding a slot in a calendar is not built yet.
publicDocs
Build this one yourself.
Try MeNothing charges. Pricing is not published yet, and the ledger says so.
Inbox Triage
you.agentbag.ai/@night-shift
Reads the overnight mail and hands you a morning digest.
triagedigestescalationwill notIt cannot reply to anyone for you. Sending is a separate permission, and it does not hold it.
privateMail
Build this one yourself.
Try MeNothing charges. Pricing is not published yet, and the ledger says so.
Front Door
you.agentbag.ai/@front-door
The public one. Answers strangers so you do not have to.
introwhat I dohow to reach mewill notIt will not repeat anything you did not publish. Its whole corpus is your public writing.
publicAccessControl
Worked examples, not customers. These six are what people in your region actually publish an agent for — each names the module its claim rests on, at that module’s real status.
Real problems, real answers.
Pick a country and a type. Watch the agent answer — then refuse what it cannot know.
“Primary DBA, Payments Platform (2021–2025). 12k writes/s peak. Authored failover runbook, led 3 zero-downtime major-version upgrades...”
12k writes/s peak
Authored failover runbook, led 3 zero-downtime major-version upgrades...
The answer came from a specific line on a specific page. Not from what the model knows — from what the owner published.
Turn an approved career story into answers a recruiter can trust. A professional in technology or healthcare can share evidence without publishing references, identity records or private interview notes.
The same agent, one question apart.
Everyone shows you the answer. The half that decides whether you would put your name on one is the other half — and it is a mechanism, not a policy.
the material was there
The question clears the gate, the matching document is inside what this asker may retrieve, and an answer leaves.
the material was never there
Same gate, narrower corpus. The document is a hole rather than a blacked-out box, so nothing has to be redacted and nothing can be talked around. You cannot un-say a sentence, so it is never said.
Findable, reachable, or neither — chosen per agent.
Almost every product ships public and private and calls it done. The one people actually want is the third. Same shelf, same address, same stranger — one thing changes per panel.
- Public
You want it found. It belongs on the shelf you send people to.
- Unlisted
You want to hand the link to specific people, and to nobody else.
- Private
It is yours. Still being built, or never meant for anyone else.
How one of them comes to exist.
Each panel draws the change, not the noun: renaming is an old address redirecting, revoking is one tether cut among several.
- 01Point it at a folder
The config lives beside the documents it governs, not in a distant admin screen.
- 02Give it a name
The name is what the agent is for. Everything downstream hangs off it.
- 03It gets an address
An address, never a credential — so it survives the session behind it being replaced.
- 04Choose who may find it
Public, unlisted or private. Three states, decided per agent rather than per account.
- 05Rename it a year later
The old address redirects permanently. Renaming never breaks what you handed out.
- 06Take the access back
Each hop carried its own token, in a ledger. Revocation is one action, not an audit.
What a deck is not.
Two of these are things we will not build rather than things we have not finished, and the difference is the point.
- Not a marketplace. There is no global page listing everyone’s agents, and there is not going to be one — discovery is federated by design, so your deck is yours and nobody enumerates it.
- Not an autonomous employee. These answer, retrieve and hand off. Nothing here goes and does things in the world on its own initiative.
- Not a booking system. Several cards here answer questions about availability; none of them holds a slot, and the ledger says calendar is on the bench rather than implying otherwise.
- Not a memory that follows you around. Retrieval from documents you filed is not the same as an agent that accumulates a private impression of you, and we do not claim the second one.
- Not free of you. Every card is grounded on material you chose and limits you set. An unattended one is a demo.