Payment safety
A setup or validation command cannot spend. Paid calls require a fee cap and an explicit confirmation flag. An ambiguous payment is reconciled; it is never automatically purchased again.
Integration kit
Connect any system.
Your application does not need its own LLM. Use typed profiles, current runtime evidence, one capped x402 payment, and a structured result.
Deterministic systems
Configure the stable contract once. Supply only current evidence for each independent call.
Coding Agent integration
Give the implementation prompt to a Coding Agent in the target repository. It adds ordinary deterministic code and offline tests—no local LLM and no paid setup call.
- 01
Open the repository
The agent first reads its architecture, security rules, wallet boundary and test conventions.
read-only - 02
Implement the native adapter
Profile mapping, runtime evidence, local validation, one-shot payment and recovery follow the same contract.
no LLM - 03
Verify without spending
Tests use fake HTTP and payment adapters. The only live setup check reads health and form endpoints.
0 USDC
Data boundary
Profiles and current evidence remain in the caller's system until one authorized request. Recovery state contains financial identifiers, never business input or output.
Execution boundary
Map returned action IDs only to allowlisted handlers and re-check local authority. ResolveSignal recommends; the caller decides whether to execute.
Machine-readable resources
All resources are direct files. The live API contract remains authoritative.