Checking registry status Spec fidreon-trust/v1, published 2026-09-22
Order intake

An agent wants to buy from you. Take the order?

Agent payments went live on real rails this month. The buyer side is handled. The supplier side is not: the order arrives from software, and nothing in it tells you whether a human authorized the amount. One call answers that before you fulfil, and leaves a signed record of the answer.

Try both, live against the registry. No key, no account.

What the answer looks like

POST https://fidreon.com/api/verify
{ "envelope": <the authority block the agent presented> }

{
  "verdict": "accept",
  "status": "active",
  "checks": {
    "signature": { "state": "valid", "verified": true, "key": "principal-... " },
    "expires_at": "2027-06-01T00:00:00Z",
    "revoked": false,
    "attenuation": "child within parent on cap, asset, expiry and scope"
  },
  "policy_hint": "Reject on reject and on any envelope you cannot verify. Treat review as manual."
}

Why this is not another directory

The answer is about one order

Not a score to browse. A decision on the transaction in front of you, at the moment it lands, with the reason attached.

It refuses what it cannot prove

A presented authorization that does not verify against a registered principal key is rejected, never waved through. That path was audited and hardened on 25 October 2026.

You keep the record

Every check returns a signed, timestamped record of what was authorized and by whom. That is the artifact a chargeback, an auditor or an insurer asks for.

Where it sits

FIDREON answers the authority question and keeps the record. Your card processor, your bank rail or your x402 endpoint still moves the money. Nothing here holds funds or takes a position in the transaction.

Pricing and how to start →