# A Server-Side Model for Gating Agent-Initiated Human-Sourced Asynchronous HTTP Tasks on Payment or Entitlement

[7 · Pay](/category/pay/)
Candidate · auto-drafted, unreviewed · confidence 60%

| A Server-Side Model for Gating Agent-Initiated Human-Sourced Asynchronous HTTP Tasks on Payment or Entitlement |
| --- |
| Category | [Pay](/category/pay/) |
| Governed by | Individual IETF Internet-Draft submission, not adopted by a working group |
| Status | Internet-Draft, Intended Status: Informational; expires 11 April 2027 |
| Phase | draft |
| Implementation | none found |
| Adoption | unmeasured |
| Version | draft-king-yew-choo-agentic-payments-01 (2026-10-08) |
| Specification | [https://datatracker.ietf.org/doc/html/draft-king-yew-choo-agentic-payments-01](https://datatracker.ietf.org/doc/html/draft-king-yew-choo-agentic-payments-01) |
| Found at | none; architectural model with no wire format or discovery element |
| Last checked | 2026-10-18 |
| Freshness | current · checked 2026-10-18 |
| Solves | Accept payments from agents, Let agents buy on behalf of a person, Delegate a user's authority to an agent, Audit what an agent did |

A Server-Side Model for Gating Agent-Initiated Human-Sourced Asynchronous HTTP Tasks on Payment or Entitlement is an agentic-web standard (document format) at step 7, Pay, governed by Individual IETF Internet-Draft submission, not adopted by a working group; its own status is "Internet-Draft, Intended Status: Informational; expires 11 April 2027" (draft). It answers: How should a server gate paid, agent-initiated asynchronous HTTP tasks on payment or entitlement so that fulfilment never precedes validation and retries do not create duplicate tasks or gate acceptances? Adoption is unmeasured, last verified 2026-10-18.

[Pay](/category/pay/) An individual-submission Internet-Draft (Informational) presenting a server-side model for paid, human-sourced asynchronous HTTP tasks initiated by software agents. It places a payment or entitlement gate before fulfilment, maps the gate to adjacent protocols (HTTP Payment authentication scheme, MPP, x402, AP2), and defines a task state machine. Under stated assumptions it yields gate-before-fulfilment safety, at most one task per idempotency key, and at most one gate acceptance per payment requirement. It defines no wire format or conformance requirements.

## Discovery and probe

none; architectural model with no wire format or discovery element

```
NONE
parse:
on absent:
```

Not probed live: no-fixed-path. candidate record; probe rule pending

## History
- 2026-10-16 — auto-drafted candidate from exa (https://datatracker.ietf.org/doc/html/draft-king-yew-choo-agentic-payments-01)

## Instances

No instances recorded yet.

## See also

## References

- Internet-Draft draft-king-yew-choo-agentic-payments-01 published 8 October 2026, Intended Status Informational. It defines no protocol, wire format, or conformance requirements, and presents a server-side payment/entitlement gate (g*) and task state machine for agent-initiated paid asynchronous HTTP tasks. — [https://datatracker.ietf.org/doc/html/draft-king-yew-choo-agentic-payments-01](https://datatracker.ietf.org/doc/html/draft-king-yew-choo-agentic-payments-01) (2026-10-08) REPORTED

[JSON](/data/protocols/agentic-payments-gating-model.json) · [Markdown](/protocols/agentic-payments-gating-model/index.md)