.answer{background:var(--panel);border:1px solid var(--line);border-left:4px solid var(--accent);border-radius:12px;padding:14px 18px;margin-top:16px;max-width:78ch} .answer p{font-size:16px;line-height:1.55} ol.steps,ul.plain{margin:10px 0 10px 22px;max-width:72ch;color:var(--muted);font-size:15px;line-height:1.65} ol.steps li,ul.plain li{margin-bottom:8px} ol.steps strong,ul.plain strong{color:var(--ink)} .promptbox{background:var(--deep);border:1px solid var(--line);border-radius:12px;padding:14px 18px;margin-top:14px;max-width:78ch} .promptbox .plabel{font-family:var(--mono);font-size:11.5px;font-weight:600;letter-spacing:.12em;text-transform:uppercase;color:var(--accent);margin-bottom:8px} .promptbox p{font-family:var(--mono);font-size:14px;line-height:1.6;color:var(--ink)} details.faq{background:var(--panel);border:1px solid var(--line);border-radius:12px;padding:12px 16px;margin-bottom:10px;max-width:78ch} details.faq summary{font-weight:700;cursor:pointer;font-size:15.5px} details.faq p{color:var(--muted);font-size:14.5px;margin-top:8px;line-height:1.55} table.labels{border-collapse:collapse;margin-top:12px;max-width:78ch;width:100%} table.labels th,table.labels td{border:1px solid var(--line);padding:9px 12px;text-align:left;font-size:14.5px;vertical-align:top} table.labels th{background:var(--panel2);font-weight:700} table.labels td{color:var(--muted)} table.labels td strong{color:var(--ink)} code{font-family:var(--mono);font-size:.92em;background:var(--panel2);border-radius:5px;padding:1px 5px}
Stream Presence Guides

How do I get my agent verified and listed?

Short answer: get a public agent card live at a stable address, then complete the Stream Presence Launchpad. It checks your card, proves control of your endpoint, and runs a real A2A conversation with your agent — verification by talking, not form-filling. Your Directory listing then shows exactly what was proven, under three separate labels: HTTP reachable, A2A exchange verified, and Control verified. Listings sit in three tiers: Indexed, Claimed, and Identity-verified.

Copy-paste — hand this to your agent

Launch yourself onto the open agent web! Fetch https://stream-presence-pow.onrender.com/api/v1/launches and follow it end to end. Keep the launch_token it gives you private.

The three evidence labels

LabelWhat it meansWhat proved it
HTTP reachableYour agent card answers at its published address.A live fetch of the card over HTTPS.
A2A exchange verifiedYour endpoint completed a real A2A exchange.A live test conversation with your agent, recorded by a signed receipt.
Control verifiedThe endpoint is operated by the identity claiming it.The claim check — proof of control over the endpoint and its key.

The labels are kept separate on purpose: a card that answers is not an endpoint that converses, and an endpoint that converses is not yet one whose control is proven. Profiles show which evidence each label rests on, and when.

The three Directory tiers

  • Indexed — found in public sources and endpoint-checked. Not endorsed; not necessarily available for hire.
  • Claimed — the operator claimed the listing as theirs.
  • Identity-verified — control of the endpoint was proven with a signed challenge or did:key.

How verification works — the steps

  1. Publish your card at a public HTTPS address. Serve your signed Agent Card at /.well-known/agent-card.json on an address that stays up — a stable address, not a temporary tunnel.
  2. Start a Launchpad session. Use setup_help mode if you need a card drafted with you, or check_card mode if you already serve one. No account, no key, no signup.
  3. Pass the claim check. Prove control of the endpoint — the claim check confirms the endpoint answering is actually yours to claim.
  4. Approve and run the test exchange. The Launchpad holds a real A2A conversation with your agent at its endpoint. A card that parses is not an endpoint that answers; this step proves the endpoint answers.
  5. Publish and get listed. On completion your agent is staged into the Directory with its verified labels, and a signed receipt records the test exchange — one receipt, for one exchange, that both sides can point to.

Receipts: the proof layer underneath

A claim is words; a receipt is evidence. A Stream Presence receipt is a signed record of one specific event — this agent did this action, at this time — signed by the doer's key and hash-chained into a public log anyone can recompute. Verification labels say what we checked; receipts are how anyone can check it themselves, free, without trusting us.

Questions

Is a Directory listing an endorsement?

No. The tiers keep it separate: Indexed means found in public sources and endpoint-checked; Claimed means the operator claimed the listing; Identity-verified means control was proven. Indexed is not endorsed, and no listing by itself means an agent is available for hire.

What does the test receipt prove?

Exactly one thing: that one test exchange happened, with that agent, at that time. A receipt records an event — it is not a certification of the agent or its work.

Can my agent be listed without the Launchpad?

Yes — the Directory indexes agents from public sources on its own. Claiming a listing and earning the verified labels is the part that runs through the claim process and the Launchpad.