Decision API / v2

Decision support for agents.

Give your agent the current evidence, constraints and available actions. Agent Advisor returns one structured next-action recommendation. Your agent keeps control of execution.

What you receive

One recommendation, with its boundaries.

Check before retrying.

An order request times out. Check its status before risking a duplicate.

Illustrative example

Request excerpt

{
  "current_state": {
    "status": "provided",
    "content": "The order request timed out. Delivery of ORDER-123 is unknown."
  },
  "capabilities": [
    {
      "id": "check_status",
      "effect": "read_only"
    }
  ]
}

Recommendation excerpt

{
  "decision": {
    "action_id": "check_status",
    "parameters": {
      "order_ref": "ORDER-123"
    },
    "pre_execution": {
      "authority": "must_verify",
      "target_freshness": "must_verify"
    }
  },
  "scope": {
    "business_action_executed_by_service": false
  }
}

Illustrative excerpts from a delivery-timeout scenario, not a complete request or live result. A final matching record can establish the goal; a pending or unavailable record cannot. These examples do not purchase a service.

One request, one purchase

Your agent handles the structured input and payment. You give it the task and spending limits.

  1. 01

    Prepare the input

    Read the live form. Fill every required field; use explicit none or unknown with an explanation only where permitted.

    GET /v2/form
  2. 02

    Review the quote

    Submit current evidence and actual capabilities. Incomplete or unsupported requests are rejected before payment.

    POST /v2/requests
  3. 03

    Authorize one payment

    Review the price and pay the initialized vault for this call using a standard x402 exact client.

    POST /v2/requests/{call_id}/pay
  4. 04

    Receive the outcome

    Retrieve the checked recommendation or reconcile failure and refund status. Do not automatically purchase another call.

    GET /v2/requests/{call_id}

Failure and refunds

Each purchase runs one analysis attempt. A paid processing failure does not count as service completion and queues a full service-fee refund to the original payer. A pending refund is not returned money; confirmation requires an onchain receipt.

Data handling

Business input and output are held in service RAM. Financial metadata is retained for recovery. Admission and analysis send supplied data to model providers under their separate data policies. This is not a provider zero-retention guarantee.

Scope

Advisor recommends an action; it does not execute the business action or independently observe its real-world outcome. Pending or missing evidence cannot prove a final goal.

For humans and agents

The same information is available as server-rendered HTML and plain Markdown. JavaScript is only a copy convenience.