ARIA AP
ARIA gives agents identity.
ARIA AP is how they use it.
ARIA AP is the exchange between an agent and the service it calls. The agent checks who the receiver is and signs each request with its own key; the receiver admits or refuses it, runs each operation once and signs a receipt; after a lost answer, either side can recover the outcome.
Specification §8 states it, in the edition of 1 November 2026. Its transport, its receipt format, its scope grammar and its retrieval rules are decided. A request that needs a person's approval is refused without one. The detailed reference is the ARIA AP API contract in the protocol repository.
WHAT IT LOOKS LIKE
A purchasing agent places an order with a supplier's API. Before it sends anything, it asks the supplier who it is and checks the answer against the identity it expects at that address. It signs the order with its own key, for this supplier and this challenge. The supplier verifies the credential and its status, checks the level and the declared scope against its own rules, records the order once and returns a signed receipt. If the answer is lost, the agent asks again under the same operation id and gets the same receipt: the order is not placed twice.
No central service in the middle. Status comes from the issuer's signed list, which names nobody you check; each party keeps its own evidence, and a person can use it later.
Who is the receiver
The agent fetches the receiver's signed identity statement, with its credential, and checks it against the DID it expects at that origin. The answer teaches the agent nothing it did not already expect: another service answering at that address gets nothing sent to it.
A signed request
Each request is signed with the agent's holder key under RFC 9421 HTTP Message Signatures, with a single-use challenge from the receiver. Change one byte and the signature no longer verifies; a copied credential cannot sign at all, because the private key never leaves its holder.
What the signature covers
What is asked, and where. A request replayed against another path does not verify.
The body, exactly. One changed digit in an amount breaks the signature.
The operation id: the same on every retry of one operation, so it runs once.
The exact credential, by URL and digest: not any credential of the same DID.
The receiver's DID. A request built for another receiver is refused here.
Issued by the receiver, used once, short-lived. A recorded request cannot be sent again.
Admission
The receiver verifies the credential and its current status with the ARIA SDK, then checks audience, level, scope, delegation and human approval, then its own rule. Only an allow runs. A refusal is a signed receipt for that attempt only: the operation is not claimed.
ADMISSION, IN ORDER
First failure ends it.
Before admission the receiver authenticates the request; those failures are unsigned, because nothing can be attributed to a key that proved nothing. Every refusal after that is signed, and none of them claims the operation.
HUMAN APPROVAL
A credential lists in hitlRequired the scopes its agent declared as needing a person's approval. When an operation's scope is one of them, a missing or invalid approval refuses the attempt (aria.approval_required, aria.approval_invalid). Operations outside that list, and the receiver's own policy, are unaffected.
Holding an operation until someone approves it is not supported: it is not part of ARIA 1.0.
SCOPES ARE DECLARED
A credential lists the scopes its agent declared: what it intends to do, in three segments, namespace:resource:action, such as payments:transfer:create or data:documents:read. Each receiver decides whether to admit them, with its own scope policy and its own rules.
A scope label alone grants nothing. New issuance uses exactly three lower-case segments, with no version, and the vocabulary is open to any activity. A receiver's policy may use namespace:resource:*, and a matching deny prevails.
Once per operation
One signed receipt format, aria-ap-receipt/1, carries the decision's HTTP status and code. A retry of the same operation gets the original receipt. A lost answer never causes a second execution or an invented rejection.
Recovery
After a lost answer, the agent signs a lookup and gets the operation's receipts back. Each party keeps its own evidence, its requests and receipts; no central service sits in the middle.
WHAT ARIA AP 1.0 COVERS, AND WHERE IT RUNS
In ARIA AP 1.0
- The transport: this RFC 9421 profile, with the receiver's identity statement, a challenge per request and the credential by reference.
- One receipt format, aria-ap-receipt/1, carrying the decision's HTTP status and code.
- When an operation needs a person's approval, a missing or invalid approval refuses the attempt; nothing is held.
- The scope grammar: three lower-case segments in new issuance, no version, compared exactly; the receiver's policy may use namespace:resource:*, where a matching deny prevails.
Not offered
- Delegation: a delegated credential is refused at admission.
- Holding an operation until a person approves it: not supported; a missing approval refuses the attempt.
- A credential sent by value: requests carry it by reference.
ARIA AP 1.0.0, and the ARIA SDK 1.0.0 it builds on, are on npm. Nothing on api.aria.bar uses ARIA AP: it runs at each receiver that adopts it.
ATP/1, DEPRECATED
ATP/1, now deprecated, was ARIA's earlier admission protocol in the edition of 7 September 2026: a receiver published a policy in a DNS TXT record at _aria-policy.<host>, the agent declared its credential and a signed intent, and the receiver evaluated them against that policy in monitor, warn or strict mode. It covered only that evaluation, and its wire binding was never published. ARIA AP covers the whole exchange and replaces it.
What stays, only as deprecated compatibility identifiers: _aria-policy records with v=ATP1, the ATP- result codes, and the schemas atp-policy-v1.json and intent-declaration-v1.json at their published URLs. ARIA AP reads none of them, so a record you published changes nothing in an ARIA AP admission.
Build on ARIA AP. Read the contract first.
The ARIA AP API contract describes each step, the request profile, admission, operations and receipts, and what it does not offer. Its package builds on the ARIA SDK's verifier; a service that only checks credentials needs only the ARIA SDK.