omni-x402-prover
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X402_NETWORK | No | Target network (base or base-sepolia). | base |
| X402_ASSET_ADDRESS | No | Base Mainnet USDC contract address (6 decimals). | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
| X402_PAY_TO_ADDRESS | Yes | EVM recipient address on Base for Base USDC payments. | |
| X402_FACILITATOR_URL | No | Facilitator URL for payment verification and on-chain settlement. | https://facilitator.payai.network |
| X402_MOCK_FACILITATOR | No | Set to 1 for offline testing/demo mode without on-chain settlement. | 0 |
| X402_PRICE_VAULT_ATOMIC | No | Price in atomic units for vault verification (6 decimals; 20000 = $0.02 USDC). | 20000 |
| X402_MAX_TIMEOUT_SECONDS | No | Maximum payment authorization window in seconds. | 60 |
| X402_PRICE_ZK_BITVEC_ATOMIC | No | Price in atomic units for ZK / BitVector verification (6 decimals; 30000 = $0.03 USDC). | 30000 |
| X402_PRICE_POLYMARKET_ATOMIC | No | Price in atomic units for Polymarket basket verification (6 decimals; 20000 = $0.02 USDC). | 20000 |
| X402_FACILITATOR_BEARER_TOKEN | No | Optional Coinbase CDP facilitator JWT token, if using the Coinbase CDP facilitator. | |
| X402_PRICE_DIFFERENTIAL_ATOMIC | No | Price in atomic units for differential consensus verification (6 decimals; 50000 = $0.05 USDC). | 50000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| x402_bazaar_catalogA | Free discovery tool: returns the Coinbase x402 Bazaar semantic catalog, available verification endpoints, pricing in Base USDC, and schema definitions. |
| x402_verify_vault_roundingC | Paid tool (20000 Base USDC atomic): Formal Z3 verification of ERC-4626 / Euler / Meteora vault share rounding, donation attacks, and zero-share inflation vulnerabilities. |
| x402_verify_polymarket_basketB | Paid tool (20000 Base USDC atomic): Formal verification of Polymarket NegRisk / Conditional Token solvency and Dutch-book net edge. |
| x402_verify_zk_or_bitvecC | Paid tool (30000 Base USDC atomic): Formal Z3 verification of ZK circuit witness uniqueness (soundness) or BitVector integer cast truncation. |
| x402_verify_differential_specB | Paid tool (50000 Base USDC atomic): Formal differential consensus equivalence verification between code_a and code_b across boundary grids. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a clearly distinct resource: one free catalog/discovery call and four paid verifiers scoped to non-overlapping domains (vault rounding, Polymarket NegRisk solvency, ZK/BitVector, differential consensus). An agent can pick the right verifier from the domain keywords alone, and the free/paid split is explicit in the descriptions.
All five names share the `x402_` prefix and four use the `verify_<target>` pattern, giving a predictable structure. The lone deviation is `x402_bazaar_catalog`, which is a noun-style discovery name rather than a verb_action, but it is still readable and its role is obvious.
Five tools is tightly scoped for a specialized formal-prover service: one discovery entrypoint plus four verifiers, each covering a distinct class of proof obligation. No tool appears redundant or padded.
The surface covers discovery plus verification for the four advertised vulnerability classes and pricing is exposed via the catalog. Minor gaps exist: there is no tool to poll status or retrieve results/history of a submitted proof, and no generic 'verify arbitrary spec' escape hatch, which agents would need for long-running Z3 jobs.