SqueezeOS — Institutional AI Market Intelligence

Aftersearch Accept

aftersearch_accept

Get accepted delivery for one immutable job with caller-supplied x402 authorization. Use this when an agent holds fresh PAYMENT-REQUIRED terms and the caller approves the spend; the caller payment_response is forwarded as the PAYMENT-SIGNATURE and SML never signs or spends. Returns the Evidence Pack plus the PAYMENT-RESPONSE receipt; on missing authorization returns a fresh 402 challenge, on a bad job_id a structured error. With valid caller authorization, settles an irreversible USDC payment and persists a receipt; the stored job remains immutable. For example, accepting a quoted job delivers the full Evidence Pack with settlement proof.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_id`	Yes	The 24-char hex job_id being settled.
`payment_response`	Yes	The caller x402 payment authorization payload for this exact job, forwarded as PAYMENT-SIGNATURE. API keys are never accepted as a substitute.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No	Whether the upstream HTTP status is 2xx; not settlement proof.
`body`	No	Unmodified upstream JSON, or bounded response text. Consult that capability's live schema.
`error`	No
`charged`	No	Present on local/transport failures; these do not establish an upstream charge.
`message`	No
`auto_spent`	No
`status_code`	No	Observed upstream HTTP status, or null when no response was obtained.
`substituted`	No
`content_type`	No
`payment_required`	No	Observed PAYMENT-REQUIRED header; a challenge does not prove payment.
`payment_response`	No	Observed PAYMENT-RESPONSE header. Assess it together with accepted delivery.
`caller_supplied_authorization`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "ok",
+        "status_code"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "description": "Canonical REST response envelope, or a local/transport rejection. Upstream data remains in body and is defined by the live capability schema.",
+  "properties": {
+    "auto_spent": {
+      "const": false
+    },
+    "body": {
+      "description": "Unmodified upstream JSON, or bounded response text. Consult that capability's live schema."
+    },
+    "caller_supplied_authorization": {
+      "type": "boolean"
+    },
+    "charged": {
+      "const": false,
+      "description": "Present on local/transport failures; these do not establish an upstream charge."
+    },
+    "content_type": {
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the upstream HTTP status is 2xx; not settlement proof.",
+      "type": "boolean"
+    },
+    "payment_required": {
+      "description": "Observed PAYMENT-REQUIRED header; a challenge does not prove payment.",
+      "type": "string"
+    },
+    "payment_response": {
+      "description": "Observed PAYMENT-RESPONSE header. Assess it together with accepted delivery.",
+      "type": "string"
+    },
+    "status_code": {
+      "description": "Observed upstream HTTP status, or null when no response was obtained.",
+      "maximum": 599,
+      "minimum": 100,
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "substituted": {
+      "const": false
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedOct 5, 2026

addedInput schema / properties / job_id / description

Added value: +"The 24-char hex job_id being settled."

addedInput schema / properties / payment_response / description

Added value: +"The caller x402 payment authorization payload for this exact job, forwarded as PAYMENT-SIGNATURE. API keys are never accepted as a substitute."

AddedSep 18, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (readOnly=false, destructive=false, idempotent=false, openWorld=true), it discloses that the caller's payload is forwarded as PAYMENT-SIGNATURE, that SML never signs or spends, that settlement of USDC is irreversible, that a receipt is persisted, that the stored job stays immutable, and the fallback behaviors (fresh 402 on missing auth, structured error on bad job_id). This is exactly the behavioral context the annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and precondition are front-loaded, and most sentences carry real information (auth forwarding, irreversibility, error paths, example). It is slightly dense and repeats the receipt concept ('persists a receipt' / 'PAYMENT-RESPONSE receipt'), keeping it out of the top band.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating settlement tool, the description covers the auth model, irreversibility, error handling, and delivery artifacts, and an output schema exists for return values. An agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already fully documented in the schema (including the job_id pattern/format and the payment_response role). The description restates rather than extends that, so baseline 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (accept / settle delivery) and resource (one immutable job) and pins it to the x402 authorization flow, letting an agent distinguish it from siblings like aftersearch_quote or aftersearch_verify_serp. The purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear precondition — 'use this when an agent holds fresh PAYMENT-REQUIRED terms and the caller approves the spend' — which tells the agent the state required before calling. It does not explicitly name the sibling (e.g. aftersearch_quote) that produces those terms or state when-not-to-use, so it stops just short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SqueezeOS — Institutional AI Market Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.