ARIA1.0

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.

RFC 9421 HTTP Message SignaturesHolder key + single-use challengearia-ap-receipt/1Once per operationNo central service

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.

01
STEP 01

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.

02
STEP 02

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

@method · @target-uri

What is asked, and where. A request replayed against another path does not verify.

content-digest

The body, exactly. One changed digit in an amount breaks the signature.

ARIA-Operation

The operation id: the same on every retry of one operation, so it runs once.

ARIA-Credential

The exact credential, by URL and digest: not any credential of the same DID.

ARIA-Audience

The receiver's DID. A request built for another receiver is refused here.

A challenge

Issued by the receiver, used once, short-lived. A recorded request cannot be sent again.

03
STEP 03

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.

Authentication · unsigned answers
01
The request
One operation the receiver describes: method, target, body and media type, query and an operation id.
400 aria.request_invalid
02
The signature
One signature by the holder key of the exact credential named, within its window, over the covered components, with a live challenge.
401 aria.authentication_failed
Admission · each refusal is a signed receipt for this attempt
03
Audience
Addressed to this receiver.
403 aria.audience_mismatch
04
The credential, now
Verified by the ARIA SDK and judged at this moment: within its validity, its status fresh and active. Unknown is never good.
403 aria.credential_revoked · 503 aria.status_unavailable
05
Level
At least the minimum the operation sets.
403 aria.level_insufficient
06
Scope
The operation's scope is one the agent declared, and the receiver's own scope policy admits it.
403 aria.scope_missing · aria.scope_denied
07
Delegation
Not supported in ARIA 1.0: a delegated credential is refused.
403 aria.delegation_unsupported
08
Human approval
When the scope is one the credential lists in hitlRequired, a valid approval must come with the request.
403 aria.approval_required
09
Your own rule
Account, amount, limits: the receiver decides, with a code of its own.
403 your.own_code
The way out
10
Allow
Claimed once for this operation, run, and answered with a signed receipt.
200 · 201 · 202

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.

04
STEP 04

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.

Completed200 · 201Done. The receipt says what was done, for which request.
Accepted202Recorded and finished later; the final receipt can be retrieved.
Rejected, the operation422The receiver refused the operation itself, with its own code. Retrying it changes nothing.
Rejected, this attempt403 · 409 · 503This attempt only: the operation is not claimed, and another attempt may succeed.
05
STEP 05

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.