Decision API / v2

Decision support for agents.

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

Integrate ResolveSignal →See an example

What you receive

One recommendation, with its boundaries.

  • A selected action with fixed parameters from the capabilities you declared.
  • A reason grounded in the supplied evidence and goal.
  • Conditions to verify before execution and conditional outcomes afterward.
  • The payment or refund state for the same independent call.

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 and build one complete request from current evidence, constraints and actual capabilities.

    GET /v2/form
  2. 02

    Prove payer control

    Sign the request-bound quote-admission challenge. This signature cannot transfer USDC.

    POST /v2/payer-challenge
  3. 03

    Create the quote

    Submit the complete request and require an HTTP 402 exact quote for 0.06 USDC to the initialized Arc vault.

    POST /v2/requests
  4. 04

    Pay and receive

    Pay the quoted call once, enforce your fee cap, and save the checked result and receipt before acting.

    POST /v2/requests/{call_id}/pay

See the Arc x402 integration guide for payer proof, quote validation and recovery.

Failure and refunds

Each purchase runs one analysis attempt. On the Arc escrow route, a paid processing failure queues a full service-fee refund to the original payer; a pending refund is not returned money until an onchain receipt confirms it.

Data handling

Business input and output are held only during processing and deleted from service RAM immediately after delivery. 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

ResolveSignal 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.