Coinbase (Coinbase for Agents / Advanced Trade) — order_filledAction contract

The agent may place an order only on an allowed product, on an allowed side, within the per-order notional limit, and within the agent's 24-hour total. The action's subject is the product the agent was told to trade (Coinbase's product id, `BTC-USD`, `TSLA-USD`). A successful trade must show up in Coinbase as an order on that product created within the window and filled; its side must be the side asked and its notional must equal the amount requested. A second order on the product within the window, an order that was cancelled, expired or rejected, or a fill busted or corrected by Coinbase within 7 days, fails the action.

Contract ID: coinbase_agent_trade
Source: https://docs.cdp.coinbase.com/api-reference/advanced-trade-api/rest-api/orders/list-orders
Retrieved: 2026-11-03
Notes: Order statuses are the reference's: PENDING, OPEN, FILLED, CANCELLED, EXPIRED, FAILED, QUEUED, CANCEL_QUEUED, EDIT_QUEUED, UNKNOWN_ORDER_STATUS. An order carries `client_order_id`, `product_id`, `side` (BUY or SELL), `order_configuration` (`quote_size` or `base_size`), `filled_size`, `filled_value`, `average_filled_price`, `total_fees`, `created_time`, `last_fill_time`. A fill carries `trade_type`: FILL, REVERSAL, CORRECTION or SYNTHETIC (https://docs.cdp.coinbase.com/api-reference/advanced-trade-api/rest-api/ orders/list-fills). The Coinbase MCP docs (https://docs.cdp.coinbase.com/ai-agents/coinbase-for-agents/ coinbase-mcp, retrieved the same day) state that hosted chat clients sometimes "draft an order but stop short of executing it" and that lower-tier models may pick the wrong product ("ETH-USD instead of ETH-USDC"); both are what the expected effects and the subject catch. The side (BUY or SELL) is limited on the action's parameter and shown in the evidence, not compared with the order: the engine's value comparisons are numeric. Limits below are template values.

What the contract checks

Each block is evaluated against read-only facts from the systems of record. The agent's own report is never used as evidence.

Unknown fields

Things the source has not published. No value is assumed for these.

order_placement_source_of_agent_orders

Contract YAML

The machine-readable action contract: allowed action, required inputs, preconditions, limits, expected and forbidden effects, window. Sign in to select it for your tenant or fork it.

# Coinbase agent trade — action contract for an agent that places an order on a Coinbase account (Coinbase for
# Agents: the Coinbase MCP tool `orders_create`, or the Advanced Trade API). Coinbase's own controls run before
# the order: the portfolio the agent is scoped to, the permissions on its key, the x402 payment cap. This contract
# runs after: it reads Coinbase's record of the order and its fills and says whether the trade the agent reported
# exists on the product it was asked to trade, once, on the right side, for the amount asked, filled within the
# window, and was not busted or corrected afterwards. Statuses and fields are Coinbase's, transcribed from the
# Advanced Trade reference (source_citation); the limits are template values to replace with your own.
id: coinbase_agent_trade
version: 1
kind: action
vendor: coinbase
vendor_display: "Coinbase (Coinbase for Agents / Advanced Trade)"
action_type: place_order
outcome_type: order_filled
claim_source: agent.actions
subject_kind: product
description: >
  The agent may place an order only on an allowed product, on an allowed side, within the per-order notional
  limit, and within the agent's 24-hour total. The action's subject is the product the agent was told to trade
  (Coinbase's product id, `BTC-USD`, `TSLA-USD`). A successful trade must show up in Coinbase as an order on
  that product created within the window and filled; its side must be the side asked and its notional must
  equal the amount requested. A second order on the product within the window, an order that was cancelled,
  expired or rejected, or a fill busted or corrected by Coinbase within 7 days, fails the action.
source_citation:
  url: "https://docs.cdp.coinbase.com/api-reference/advanced-trade-api/rest-api/orders/list-orders"
  retrieved: "2026-11-03"
  title: "Coinbase Advanced Trade API — List Orders, List Fills; Coinbase MCP for Agents"
  notes: >
    Order statuses are the reference's: PENDING, OPEN, FILLED, CANCELLED, EXPIRED, FAILED, QUEUED,
    CANCEL_QUEUED, EDIT_QUEUED, UNKNOWN_ORDER_STATUS. An order carries `client_order_id`, `product_id`, `side`
    (BUY or SELL), `order_configuration` (`quote_size` or `base_size`), `filled_size`, `filled_value`,
    `average_filled_price`, `total_fees`, `created_time`, `last_fill_time`. A fill carries `trade_type`: FILL,
    REVERSAL, CORRECTION or SYNTHETIC (https://docs.cdp.coinbase.com/api-reference/advanced-trade-api/rest-api/
    orders/list-fills). The Coinbase MCP docs (https://docs.cdp.coinbase.com/ai-agents/coinbase-for-agents/
    coinbase-mcp, retrieved the same day) state that hosted chat clients sometimes "draft an order but stop
    short of executing it" and that lower-tier models may pick the wrong product ("ETH-USD instead of
    ETH-USDC"); both are what the expected effects and the subject catch. The side (BUY or SELL) is limited on
    the action's parameter and shown in the evidence, not compared with the order: the engine's value
    comparisons are numeric. Limits below are template values.
unknown_fields: [order_placement_source_of_agent_orders]
action:
  window: "1h"
  limits:
    - param_max: {param: amount, max: 1000}
    - param_in: {param: side, values: [BUY, SELL]}
  aggregate_limits:
    - aggregate_exceeds:
        source: coinbase
        type: order_created
        attr: quote_value
        max: 5000
        over: "24h"
        by: agent
        message: "This agent's orders over 24 hours exceed the daily notional total"
  expected_effects:
    - effect_observed:
        source: coinbase
        type: order_created
        message: "No order on the intended product was created in Coinbase"
    - effect_observed:
        source: coinbase
        type: order_filled
        message: "The order did not fill: it was placed but no trade happened"
  forbidden_effects:
    - effect_count_exceeds: {source: coinbase, type: order_created, max: 1}
    - effect_attr_differs:
        source: coinbase
        type: order_created
        attr: quote_value
        equals_param: amount
        tolerance: 0.01
        message: "The order's notional differs from the amount requested"
    - effect_observed:
        source: coinbase
        type: order_failed
        message: "The order was cancelled, expired or rejected"
  reversed_by:
    - effect_observed:
        source: coinbase
        type: order_reversed
        within: "7d"
        message: "A fill of this order was busted or corrected by Coinbase"
  unverifiable_if:
    - missing_fact_source: [coinbase]
billing:
  unit_price: 0
  currency: USD

Use this contract See it applied in a sample verification