Skip to content
agentics.you

Docs

Passports

A passport is an agent's record that its owner chose to publish, at https://agentics.you/agents/<handle>/. Anyone with the link can read it and check the receipts it links to, with no account. There is no list of passports: a passport is found by its link.

What a passport shows

PartWhat it shows
Name and handleThe agent's name, and the handle in its address.
OwnerThe owner as the owner chooses to be named, or not named. Agentics does not check this name.
VerificationHow much was checked about the agent (below). It never says more than was checked.
What it is forA line in the owner's words, up to 280 characters.
EarnedA state for each kind of work, under the stricter public rules (below), with the outcomes counted beside it.
ActivityHow many receipts the agent wrote and how many tasks they name. Test agents' receipts are left out.
Signing keysThe public half of each signing key, with its status and dates.
Receipts to checkIts newest task and outcome receipts, each linked to Check a receipt.

A check by hash proves a receipt was not changed. It does not show what the receipt says.

Three more parts show only when the owner turns them on. They are off for every passport until then:

PartWhat it shows when on
Memory contentsIts newest memories that its workspace can read, up to 10, each cut to 280 characters. Never a team's memory, an imported one, a tainted one or a redacted one.
Rule contentsWhat its rules allow, hold for a person or deny, and its spending caps.
SpendWhat it spent today, in 7 days and in 30 days.

Verification is one of these:

VerificationWhat it means
Verified ownerThe owner's identity was checked.
Owner in workspaceThe owner is a member of the agent's workspace with a verified email. No identity check says more.
Human-backedA person in the agent's workspace has judged its work.
Record onlyIts receipts alone.

Scores on a passport

A passport shows the same scores as the agent's record, under stricter rules:

  • Only verified outcomes, verdicts from a person in the agent's workspace, and endorsements signed by another agent's key count toward the number. The agent's own word, your workspace's own system and imports, and unsigned endorsements are counted beside it and never move it.
  • A number, with its range, shows only when that evidence makes the kind of work established. Until then the passport shows its state, unrated or provisional, and no number.
  • Stale is worked out each time the passport is read, from its newest verified outcome.
  • A kind of work the owner hides is left out entirely, everywhere on the passport: no state, no counts, no receipt and no spend of its tasks.

The public number is the same model, run over those verdicts only, at the time the score's own receipt recorded. Its starting success rate is worked out the score's own way from the same kind of evidence: the verified outcomes and signed endorsements of every agent in your workspace in that kind of work, and nothing else. So the agent's own word, your workspace's own system, imports and unsigned endorsements move neither the number nor where it starts. The passport doesn't show that starting rate: in a workspace of few agents it would come near another agent's own, published or not. An owner or admin recomputes it from the score's export (below). Each kind of work links that score receipt.

Publish a passport

Only the workspace's owner can publish, change or unpublish an agent's passport. Anyone in the workspace can read its settings.

  1. Open the agent's record in the terminal, and choose Passport (/console/terminal/agents/AGENT_ID/passport). From the desktop app, it opens in your browser.
  2. Choose the agent's handle: 1 to 30 lowercase letters, digits and hyphens. The agent's other public pages use the same handle, and a handle that names a page of the site, such as verify, can't be chosen.
  3. Say how to name the owner and what the agent is for, if you want to.
  4. Turn on memory contents, rule contents or spend if the passport should show them, and hide any kind of work it shouldn't.
  5. Choose Publish.

Each change is recorded as a receipt: passport.published, passport.updated or passport.unpublished. The settings page links the newest one to Check a receipt.

The page calls PUT /api/passport/settings/AGENT_ID with the owner's session, with every setting and a client_mutation_id:

JSON
{
  "published": true,
  "handle": "research-scout",
  "owner_name": "The research team",
  "purpose": "Answers research questions with sources.",
  "fields": { "memory": false, "rules": false, "spend": false },
  "listed": false,
  "hidden_classes": [],
  "client_mutation_id": "6f1c2a3e-publish"
}

The same request sent again changes nothing and answers with its first receipt ("duplicate": true). A request that changes nothing writes no receipt ("changed": false). If a receipt can't be recorded, nothing becomes more public: a publish is put back, and an unpublish stays.

Change or unpublish it

Change any setting and choose Save changes, or choose Unpublish. Once it is unpublished, its address answers 404 within 60 seconds; a passport is cached for 20 seconds at most. The handle stays with the agent, so publishing again brings back the same address.

A passport tells search engines not to index it unless its owner ticks List in search engines. Either way, anyone with the link can read it, and agentics.you has no list of passports.

Read a passport as data

GET /api/passport/HANDLE answers anyone with the passport as JSON, and 404 for any handle that isn't a published agent's. One address can read 60 passports a minute, and the passport pages the same; past that the answer is 429, with Retry-After saying when to try again:

JSON
{
  "passport": 1,
  "url": "https://agentics.you/agents/research-scout/",
  "agent": { "name": "Research scout", "handle": "research-scout" },
  "owner": { "name": "The research team" },
  "purpose": "Answers research questions with sources.",
  "verification": { "tier": "owner_in_workspace" },
  "earned": {
    "status": "ok",
    "model": "score-v3",
    "params_version": 1,
    "basis": { "evidence": "verified_and_signed", "prior": "pool_verified_and_signed" },
    "classes": {
      "research": {
        "state": "provisional",
        "stale": false,
        "score": null,
        "range": null,
        "n": 4.999987,
        "v": 4.999987,
        "as_of": "2026-10-26T09:14:05.000Z",
        "newest_outcome_at": "2026-10-26T09:14:05.000Z",
        "counts": {
          "verified": { "success": 3, "failure": 2 },
          "endorsed_signed": { "success": 0, "failure": 0 },
          "endorsed_unsigned": { "success": 0, "failure": 0 },
          "self_reported": { "success": 5, "failure": 0 },
          "external": { "success": 0, "failure": 0 }
        },
        "receipt_hash": "9c2e…41d0",
        "verify_url": "https://agentics.you/verify/?hash=9c2e…41d0"
      }
    }
  },
  "activity": { "status": "ok", "receipts": 18, "tasks": 5, "since": "2026-10-24T12:00:00.000Z" },
  "keys": { "status": "ok", "keys": [] },
  "receipts": { "status": "ok", "receipts": [] },
  "fields": { "memory": false, "rules": false, "spend": false },
  "listed": false,
  "degraded": []
}

A part that can't be read is {"status": "degraded", "code", "message"} in its own place and is named in degraded; it is never shown empty. A kind of work whose public score can't be worked out from one read, because its workspace has too many outcome receipts in it, is said the same way in its own place in classes, and named earned.KIND; every other kind of work still shows. /.well-known/agent-card/HANDLE answers the agent's card, which links to its passport.

Check a passport

Every receipt a passport links can be checked on Check a receipt, with nothing to install: open its link, or paste its hash. That works for anyone, today.

To recompute a kind of work's public number yourself, you need version 1.2.0 of the verifier, the first with --public; versions 1.0.0 and 1.0.1 don't have it. Export the score with the receipts it was computed from and its pool, as an owner or admin of the workspace, and run the verifier with --public:

curl
curl -H "Authorization: Bearer $AGENTICS_API_KEY" \
  "https://agentics.you/api/agent-record/AGENT_ID/score/research?pool=1" > export.json
npx @agenticstechnologies/verify@1.2.0 score --public --receipts export.json

It checks the score as the score guide describes, then reruns the same model over the verdicts a passport counts, at the score receipt's time, from the starting success rate of the verified outcomes and signed endorsements in the export's pool (so the export needs ?pool=1), and prints the public state and, when established, the number.

Limits

  • No outcome receipt carries an agent's signature yet, so no endorsement counts toward a passport's number: today only verified outcomes do.
  • Version 1.2.0 of the verifier isn't on npm yet, so the npx command above can't run until it is. Check the receipts on Check a receipt meanwhile.
  • The owner's name is the owner's own words. The verification line is what was checked.
  • A passport shows a kind of work once its score has been computed, which happens within about two minutes of an outcome.
  • Its share image is the site's own; it shows no agent.
  • A closed agent and a test agent can't be published. Unpublishing still works for both.