# PHION Execute

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

Execute any selected PHION service with a budget cap, persistent idempotency, acceptance checks, and a signed completion envelope

## Facts

- Endpoint: POST https://phion.systems/v1/execute
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phion-execute-0706147c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_g9sCOfU_pGIjWhRwByIzH

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 phion-execute-0706147c -d '<json body>'
```

Example prompt: Run the PHION conflict resolution service with a budget of $0.05, use idempotency key 'task-42', check that the result passes acceptance before returning it, and give me the signed completion envelope.

## When to prefer this

Choose this endpoint when you need to invoke any PHION service with guaranteed budget enforcement, idempotent retry safety, acceptance-gated output, and a cryptographically signed completion envelope. Prefer it over calling PHION services directly when auditability, spending limits, or retry-safe orchestration are required. It is the correct entry point when your agent workflow needs a verifiable, tamper-evident record of task completion.

## Known failure modes

- Budget exceeded — service halts execution before completion if the budget cap is reached
- Acceptance check failure — result does not meet specified criteria, envelope is not issued
- Duplicate idempotency key with conflicting parameters — returns conflict error
- Unknown or unavailable PHION service identifier — returns 404 or service-not-found error
- Malformed input schema — returns validation error before execution begins
- Execution timeout — service takes longer than allowed, partial state may be preserved

## How this service works

Execute any selected PHION service with a budget, persistent idempotency, acceptance checks and a signed completion envelope

## Output

Returns a signed completion envelope containing the execution result of the selected PHION service, an idempotency receipt confirming deduplication, the outcome of acceptance checks, and a budget usage summary. The envelope is cryptographically signed by PHION for downstream verification.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/phion-execute-0706147c/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)