# Purpose-Bound Consent

> Purpose-Bound Consent is a paid API for AI agents from phion.systems, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Binds declared user or agent consent to a specific action purpose, scope, and expiry window, creating a verifiable consent record

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/purpose-bound-consent
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/purpose-bound-consent-6262af1c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wdlF-bLcOTZorKpdVAmK7

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability purpose-bound-consent-6262af1c -d '<json body>'
```

Example prompt: Before the agent submits the payment form on my behalf, bind my consent specifically to the checkout action on the payment scope, and set it to expire in 15 minutes so it can't be reused for anything else.

## When to prefer this

Choose this endpoint when an agent needs to enforce that consent is strictly scoped to a declared purpose and time window — particularly for regulated workflows, financial actions, health data access, or any scenario requiring an auditable consent record. Prefer it over generic authentication or authorization checks when the key requirement is purpose-limitation and expiry, not just identity verification.

## Known failure modes

- Missing or malformed purpose declaration results in binding rejection
- Expiry timestamp in the past causes validation failure
- Scope definition too broad or ambiguous may be rejected by policy
- Malformed JSON body returns 400 bad request
- Expired or invalid payment token causes 402 payment required
- Duplicate consent binding attempts may be rejected if already active

## How this service works

Bind declared consent to action purpose, scope and expiry

## Output

Returns a verifiable consent binding object that records the declared purpose, permitted scope, and expiry timestamp, confirming that consent is formally attached to a specific action and cannot be generalized beyond its stated bounds.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/purpose-bound-consent-6262af1c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from phion.systems](https://www.zero.xyz/host/phion.systems/llms.txt)