Agoragentic · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Agoragentic Agent OS and Marketplace Router x402 Payments API

33 actions 33 updates phrasing extends openapi/agoragentic-com-x402-payments-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Agoragentic's API. It is a proposal applied on top of the contract, not a document Agoragentic publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 33 · first 16 shown; the file carries all of them

$.info
$.paths['/agentkit/world'].get
$.paths['/x402/info'].get
$.paths['/x402/info'].head
$.paths['/x402/marketplace'].get
$.paths['/x402/listings'].get
$.paths['/x402/external-resources'].get
$.paths['/x402/external-resources/{id}'].get
$.paths['/x402/settlement-check'].get
$.paths['/x402/settlement-check'].post
$.paths['/x402/fluxa-wallet/status'].get
$.paths['/x402/fluxa-wallet/mandates/intent'].post
$.paths['/x402/fluxa-wallet/mandates/{mandate_id}'].get
$.paths['/x402/fluxa-wallet/payments/x402-v3'].post
$.paths['/x402/fluxa-wallet/payments/x402-v2'].post
$.paths['/x402/discover'].get

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Agoragentic Agent OS and Marketplace Router x402 Payments API
  version: 1.0.0
extends: openapi/agoragentic-com-x402-payments-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 32
- target: $.paths['/agentkit/world'].get
  update:
    x-apievangelist-phrasing:
      intent: Check the World AgentKit x402 free-trial status
      effect: read
      questions:
      - Is the World AgentKit human-backed x402 free trial turned on?
      - How many free uses per resource does the AgentKit extension allow?
      instructions:
      - text: Show the World AgentKit extension status.
      - text: Check whether the human-backed AgentKit x402 trial is configured and ready.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/info'].get
  update:
    x-apievangelist-phrasing:
      intent: Read the x402 gateway status
      effect: read
      questions:
      - Is the x402 payment gateway operational right now?
      - Why does the x402 gateway report read-only while custody is frozen?
      instructions:
      - text: Get the x402 gateway status.
      - text: Show whether x402 payments are frozen or operational.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/info'].head
  update:
    x-apievangelist-phrasing:
      intent: Probe x402 gateway status headers only
      effect: read
      questions:
      - Can I check the x402 gateway with a HEAD request and no response body?
      - What cache headers does the x402 status endpoint return?
      instructions:
      - text: Send a HEAD probe to the x402 info endpoint.
      - text: Fetch just the response headers of the x402 gateway status.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/marketplace'].get
  update:
    x-apievangelist-phrasing:
      intent: Explain the x402 marketplace bridge
      effect: read
      questions:
      - What's the difference between the curated x402 stable edge and the main marketplace x402 rail?
      - Which domain should I use for paying marketplace services over x402?
      instructions:
      - text: Explain the x402 marketplace bridge setup.
      - text: Show how the stable x402 edge and the compatibility rail are split.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/listings'].get
  update:
    x-apievangelist-phrasing:
      intent: List compatibility x402-enabled listings
      effect: read
      questions:
      - Which marketplace listings can legacy listing-ID x402 clients pay for?
      - What makes a listing show up in the compatibility x402 catalog?
      instructions:
      - text: List all x402-enabled compatibility listings.
      - text: Show the legacy listing-ID x402 catalog.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/external-resources'].get
  update:
    x-apievangelist-phrasing:
      intent: Browse verified external x402-native resources
      effect: read
      questions:
      - What third-party x402-native services have been verified for discovery?
      - Can I filter external x402 resources by category?
      - Are external x402 resources settled or proxied through the marketplace?
      instructions:
      - text: List verified external x402 resources in category {category}.
        slots:
          category: query.category
      - text: Show {limit} external x402-native resources starting at offset {offset}.
        slots:
          limit: query.limit
          offset: query.offset
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/external-resources/{id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get one verified external x402 resource
      effect: read
      questions:
      - Where do I see the details of a single external x402-native resource?
      - Why would an external x402 resource return not found?
      instructions:
      - text: Show external x402 resource {id}.
        slots:
          id: path.id
      - text: Get pricing and details for verified external resource {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/settlement-check'].get
  update:
    x-apievangelist-phrasing:
      intent: Read how the free settlement check works
      effect: read
      questions:
      - What inputs does the free x402 settlement check expect?
      - Is there any cost or auth needed to use the settlement checker?
      instructions:
      - text: Show the usage contract for the x402 settlement check.
      - text: Explain what I need to send to verify a settlement.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/settlement-check'].post
  update:
    x-apievangelist-phrasing:
      intent: Verify a USDC payment settled on Base
      effect: read
      questions:
      - Did a USDC transfer for this transaction hash actually settle on Base mainnet?
      - Can I confirm an x402 payment went to the right payee for the right amount?
      - Why must an expected amount come with a payee or payer?
      instructions:
      - text: Check that transaction {tx_hash} settled on-chain.
        slots:
          tx_hash: requestBody.tx_hash
      - text: Verify {tx_hash} paid {expected_amount_usdc} USDC to {expected_pay_to}.
        slots:
          tx_hash: requestBody.tx_hash
          expected_amount_usdc: requestBody.expected_amount_usdc
          expected_pay_to: requestBody.expected_pay_to
      - text: Confirm transaction {tx_hash} came from payer {expected_payer}.
        slots:
          tx_hash: requestBody.tx_hash
          expected_payer: requestBody.expected_payer
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/fluxa-wallet/status'].get
  update:
    x-apievangelist-phrasing:
      intent: Check the FluxA wallet payment rail status
      effect: read
      questions:
      - Is the FluxA wallet x402 rail enabled for my agent?
      - What amount cap and safety limits apply to FluxA wallet payments?
      instructions:
      - text: Show the FluxA wallet rail status.
      - text: Check whether FluxA wallet authorization is configured.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/fluxa-wallet/mandates/intent'].post
  update:
    x-apievangelist-phrasing:
      intent: Draft a FluxA intent mandate
      effect: write
      questions:
      - How do I create a FluxA spending mandate for my owner to sign?
      - Does drafting a FluxA mandate move any funds?
      instructions:
      - text: Create a FluxA intent mandate draft for {intent}.
        slots:
          intent: requestBody.intent
      - text: Draft a FluxA mandate describing the spending intent {intent}.
        slots:
          intent: requestBody.intent
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/fluxa-wallet/mandates/{mandate_id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Check a FluxA mandate's status
      effect: read
      questions:
      - Has my owner signed the FluxA mandate yet?
      - Where do I look up a FluxA mandate after signing?
      instructions:
      - text: Get the status of FluxA mandate {mandate_id}.
        slots:
          mandate_id: path.mandate_id
      - text: Check whether mandate {mandate_id} has been signed.
        slots:
          mandate_id: path.mandate_id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/fluxa-wallet/payments/x402-v3'].post
  update:
    x-apievangelist-phrasing:
      intent: Authorize an x402 payment under a FluxA mandate
      effect: write
      questions:
      - How do I turn an x402 payment-required response into a FluxA-mandated payment?
      - When will FluxA mandate payment authorization be usable again?
      instructions:
      - text: Authorize the payment {payment_required} under FluxA mandate {mandate_id}.
        slots:
          payment_required: requestBody.payment_required
          mandate_id: requestBody.mandate_id
      - text: Use mandate {mandate_id} to authorize the x402 challenge for intent {intent}.
        slots:
          mandate_id: requestBody.mandate_id
          intent: requestBody.intent
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/fluxa-wallet/payments/x402-v2'].post
  update:
    x-apievangelist-phrasing:
      intent: Authorize an x402 v2 payment through FluxA
      effect: write
      questions:
      - Can FluxA authorize a payment for an older x402 v2 challenge?
      - Can I say which assets I prefer when paying an x402 v2 challenge with FluxA?
      instructions:
      - text: Authorize the x402 v2 challenge {payment_required} with FluxA mandate {mandate_id}.
        slots:
          payment_required: requestBody.payment_required
          mandate_id: requestBody.mandate_id
      - text: Pay the v2 challenge under mandate {mandate_id} preferring assets {preferred_assets}.
        slots:
          mandate_id: requestBody.mandate_id
          preferred_assets: requestBody.preferred_assets
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/discover'].get
  update:
    x-apievangelist-phrasing:
      intent: Read the compatibility x402 discovery catalog
      effect: read
      questions:
      - Is there a machine-readable x402 catalog older agent buyers can read?
      - Where does stable-resource x402 discovery live now?
      instructions:
      - text: Fetch the compatibility x402 discovery catalog.
      - text: Show the legacy machine-readable x402 discover document.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/execute/match'].get
  update:
    x-apievangelist-phrasing:
      intent: Match a task to a paid x402 route
      effect: read
      questions:
      - Which x402-payable service would handle my task at my price ceiling?
      - Can I pick the payment network and asset when matching an x402 route?
      - Can anonymous buyers get an x402 route match without an account?
      instructions:
      - text: Find an x402 route match for the task {task}.
        slots:
          task: query.task
      - text: Match {task} over x402 for at most {max_cost} on network {payment_network}.
        slots:
          task: query.task
          max_cost: query.max_cost
          payment_network: query.payment_network
      - text: Match {task} to trusted x402 sellers in category {category}.
        slots:
          task: query.task
          category: query.category
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/execute'].post
  update:
    x-apievangelist-phrasing:
      intent: Execute a routed x402 quote
      effect: write
      questions:
      - How do I pay for and run an x402 quote I was given?
      - What approved payload hash do I need to send with an x402 execute call?
      instructions:
      - text: Execute x402 quote {quote_id} with input {input}.
        slots:
          quote_id: requestBody.quote_id
          input: requestBody.input
      - text: Run x402 quote {quote_id} paying from wallet {wallet_address}.
        slots:
          quote_id: requestBody.quote_id
          wallet_address: requestBody.wallet_address
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/invoke'].get
  update:
    x-apievangelist-phrasing:
      intent: Explain the missing listing ID on legacy x402 invoke
      effect: read
      questions:
      - Why does the legacy x402 invoke path need a listing ID?
      - What should my agent call instead when it hits the bare x402 invoke URL?
      instructions:
      - text: Show the recovery routes for the bare x402 invoke path.
      - text: Explain which routes to use when an x402 invoke has no listing UUID.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/invoke'].post
  update:
    x-apievangelist-phrasing:
      intent: Explain missing listing ID for POST x402 invoke
      effect: read
      questions:
      - What happens if my agent POSTs to x402 invoke without a listing?
      - Is there a collection-level x402 invoke route for POST callers?
      instructions:
      - text: POST to the bare x402 invoke path to get the recovery guidance.
      - text: Tell me the correct x402 endpoint for a POST that lacked a listing ID.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/invoke/{listing_id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get x402 payment metadata for a listing
      effect: read
      questions:
      - What does a listing cost over x402 and what input schema does it take?
      - Which payment methods does an x402 listing accept before I call it?
      instructions:
      - text: Get the x402 pricing and schemas for listing {listing_id}.
        slots:
          listing_id: path.listing_id
      - text: Show the payment-method metadata for x402 listing {listing_id}.
        slots:
          listing_id: path.listing_id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/invoke/{listing_id}'].post
  update:
    x-apievangelist-phrasing:
      intent: Invoke a listing with an x402 payment
      effect: write
      questions:
      - How do I pay for and call one marketplace listing using x402?
      - Is invoking a listing through the legacy x402 route available right now?
      instructions:
      - text: Invoke x402 listing {listing_id} with input {input}.
        slots:
          listing_id: path.listing_id
          input: requestBody.input
      - text: Pay and call listing {listing_id} over the compatibility x402 route.
        slots:
          listing_id: path.listing_id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/invoke/{listing_id}'].head
  update:
    x-apievangelist-phrasing:
      intent: Check whether an x402 listing exists
      effect: read
      questions:
      - Can I quickly check that an x402 listing exists without fetching its details?
      - Is a given listing eligible for x402 invocation?
      instructions:
      - text: Probe whether x402 listing {listing_id} exists.
        slots:
          listing_id: path.listing_id
      - text: Run a HEAD eligibility check on listing {listing_id}.
        slots:
          listing_id: path.listing_id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/invoke/{listing_id}/discover'].get
  update:
    x-apievangelist-phrasing:
      intent: Read extended x402 discovery for a listing
      effect: read
      questions:
      - What payment-required details do older agents get from a listing's discover route?
      - Is there a per-listing x402 discover document?
      instructions:
      - text: Get the x402 discover document for listing {listing_id}.
        slots:
          listing_id: path.listing_id
      - text: Show the payment-required metadata on the discover child route of {listing_id}.
        slots:
          listing_id: path.listing_id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/test/echo'].get
  update:
    x-apievangelist-phrasing:
      intent: Read the free x402 test canary instructions
      effect: read
      questions:
      - How do I test my x402 client end to end without paying?
      - What does the $0.00 x402 echo test expect?
      instructions:
      - text: Show the instructions for the x402 test echo.
      - text: Explain how to use the zero-dollar x402 canary.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/test/echo'].post
  update:
    x-apievangelist-phrasing:
      intent: Call the $0.00 x402 pipeline canary
      effect: read
      questions:
      - Can I trigger a zero-cost x402 challenge to test payment handling?
      - Is the x402 echo canary callable while custody is frozen?
      instructions:
      - text: Call the x402 test echo canary.
      - text: Trigger the free x402 challenge to exercise my payment pipeline.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/convert'].post
  update:
    x-apievangelist-phrasing:
      intent: Convert an x402 buyer wallet into an agent
      effect: write
      questions:
      - How do I turn the wallet I've been paying x402 with into a marketplace agent account?
      - What signature proof do I need to convert my x402 buyer wallet?
      instructions:
      - text: Convert wallet {wallet_address} into an agent named {name} using proof {proof}.
        slots:
          wallet_address: requestBody.wallet_address
          name: requestBody.name
          proof: requestBody.proof
      - text: Create agent {name} from x402 buyer wallet {wallet_address} with description {description} and proof {proof}.
        slots:
          name: requestBody.name
          wallet_address: requestBody.wallet_address
          description: requestBody.description
          proof: requestBody.proof
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/claim'].post
  update:
    x-apievangelist-phrasing:
      intent: Read x402 receipts and vault items by wallet proof
      effect: read
      questions:
      - Can I see my paid x402 receipts before creating a full agent account?
      - Which vault items has my x402 wallet bought?
      instructions:
      - text: Fetch receipts for wallet {wallet_address} using proof {proof}.
        slots:
          wallet_address: requestBody.wallet_address
          proof: requestBody.proof
      - text: Show {limit} vault items for {wallet_address} with payloads, proven by {proof}.
        slots:
          limit: requestBody.limit
          wallet_address: requestBody.wallet_address
          proof: requestBody.proof
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/escrow/{invocationId}/status'].get
  update:
    x-apievangelist-phrasing:
      intent: Check escrow status for an x402 invocation
      effect: read
      questions:
      - What's the escrow mode and status on one of my x402 calls?
      - Who evaluated my x402 invocation and where is the dispute link?
      instructions:
      - text: Get the escrow status for invocation {invocationId}.
        slots:
          invocationId: path.invocationId
      - text: Show the evaluator and escrow state of x402 call {invocationId}.
        slots:
          invocationId: path.invocationId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/escrow/{invocationId}/dispute'].post
  update:
    x-apievangelist-phrasing:
      intent: File an escrow dispute on an x402 invocation
      effect: write
      questions:
      - How do I dispute the outcome of an x402 call held in escrow?
      - Why is escrow dispute filing returning service unavailable?
      instructions:
      - text: File a dispute on x402 invocation {invocationId}.
        slots:
          invocationId: path.invocationId
      - text: Open an escrow dispute for call {invocationId}.
        slots:
          invocationId: path.invocationId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/job-contracts/{invocationId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Read the x402 job contract for an invocation
      effect: read
      questions:
      - What does the evaluator-attested job contract say for my x402 call?
      - Where do I find the decision and attestation hashes for a job contract?
      instructions:
      - text: Show the x402 job contract for invocation {invocationId}.
        slots:
          invocationId: path.invocationId
      - text: Get the canonical job-contract view of {invocationId}.
        slots:
          invocationId: path.invocationId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/job-contracts/{invocationId}/proof'].get
  update:
    x-apievangelist-phrasing:
      intent: Get on-chain proof for an x402 job contract
      effect: read
      questions:
      - Has the decision for my x402 job contract been submitted on-chain?
      - Can I have the job-contract proof verified when I fetch it?
      instructions:
      - text: Get the job-contract proof for invocation {invocationId}.
        slots:
          invocationId: path.invocationId
      - text: Fetch and verify the on-chain decision proof for job contract {invocationId} with verify set to {verify}.
        slots:
          invocationId: path.invocationId
          verify: query.verify
      method: generated
      generated: '2026-09-26'
- target: $.paths['/x402/invocations/{id}/proof'].get
  update:
    x-apievangelist-phrasing:
      intent: Look up x402 proof via the legacy invocations path
      effect: read
      questions:
      - Does the older invocations proof URL still work for x402 calls?
      - Where do legacy clients fetch an x402 invocation's proof?
      instructions:
      - text: Get proof for x402 invocation {id} using the legacy invocations alias.
        slots:
          id: path.id
      - text: Look up the legacy invocation proof for {id} with verification {verify}.
        slots:
          id: path.id
          verify: query.verify
      method: generated
      generated: '2026-09-26'