---
title: "One safe action through the full governed NOMOS chain - signed, verifiable execution receipt"
method: POST
path: "/v2/nomos_full_chain_verification"
tags: ["nomos"]
---

# One safe action through the full governed NOMOS chain - signed, verifiable execution receipt

`POST /v2/nomos_full_chain_verification`

Full-Chain Governed Verification: run one safe, read-only machine action through the complete NOMOS Machine Economy Trust Chain and get back a cryptographically verifiable execution proof. The call binds your payment, a stated intent, a pinned capability and offer, a NOMOS admission decision (which enforces current CISA-KEV-derived OracleNet security-freshness evidence), the execution and the response bytes into one Ed25519-signed execution receipt you can verify yourself against the public JWKS (https://feedoracle.io/.well-known/nomos-execution-jwks.json). Read-only; no asset movement besides the x402 payment itself. Request size limit (separate from schema validation): the request object is rejected when its re-serialised JSON exceeds 2048 UTF-8 bytes; this is measured on the parsed-and-re-serialised object, so whitespace and key order in the raw HTTP body do not count towards it. Claim boundary: EXECUTION_BOUND_PROOF (estate-signed evidence, not an independent third-party attestation, not a certification).

## Request body

- object
  - `intent` 'verify_full_chain', required — Fixed action selector. The only accepted value is verify_full_chain.
  - `client_nonce` string, required — Your correlation nonce; echoed and bound into the signed intent digest. 8-64 characters, letters, digits, underscore and hyphen only.
  - `requested_capability` 'nomos_full_chain_verification' — Optional legacy compatibility field. Omit it: normal callers do not need it. If sent, it must equal the canonical capability id, otherwise the request is rejected. It carries no caller authority - it neither selects nor widens the executed capability, and the value is discarded after validation; execution always uses the server-side capability constant.

## Response `200`

Success (synthetic example)

## Other responses

- `400` — Bad Request — invalid or missing parameters.
- `402` — Payment Required (x402 v2): payment requirements are in the PAYMENT-REQUIRED response header (accepts[]); retry with the PAYMENT-SIGNATURE header (USDC on Base, eip155:8453). Success carries the PAYMENT-RESPONSE settlement header. The legacy X-PAYMENT header is not accepted on /v2 routes.

## Changes

- **2026-08-14** `f7adb705501e` — 2 breaking, 2 info
  - request property `intent` was restricted to a list of enum values
  - added the pattern `^[A-Za-z0-9_-]{8,64}$` to the request property `client_nonce`
  - added the new optional request property `requested_capability`
  - added the new `verify_full_chain` enum value to the request property `intent`
- **2026-08-11** `58e4e92ec5fa` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/tooloracle/apis/tooloracle-mcp-platform/changes/v2/nomos_full_chain_verification/post.md)

---

[API](https://skmtc.dev/tooloracle/apis/tooloracle-mcp-platform.md) · [All operations](https://skmtc.dev/tooloracle/apis/tooloracle-mcp-platform/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/tooloracle/tooloracle-mcp-platform/revisions/516d2ea6ca6d/schema)