Agent
x402 payment header. Flow:
- Make the request without this header → receive
402 Payment Requiredand, for protected routes, aPAYMENT-REQUIREDheader describing accepted payment requirements - Create the x402 payment payload for USDC on Base (chain 8453), typically via
@x402/coreand the CDP facilitator atapi.cdp.coinbase.com - Retry the request with this header set to the encoded payment payload
Successful 2xx responses may include a PAYMENT-RESPONSE settlement receipt. See https://github.com/rigoblock/agentic-operator/blob/main/AGENTS.md for full integration.
RigoBlock vault (smart pool) address for vault-scoped operations
0xYourVaultAddressOptional request-scoped context snippets (for example markdown excerpts) injected into the model prompt for this request.
Target chain context
basePossible values: AI response with DeFi action or analysis
AI-generated response text
Reasoning trace from the model, when available.
Ordered list of model identifiers that contributed to this output.
Model that authored the final natural-language output (or 'tooling' when output is tool-native).
Bad request
Payment required (x402). Pay in USDC on Base and retry with X-Payment header.
Last updated