Settled

Claim your endpoints (sellers)

settled_claim

Idempotent

Free. For sellers: claim every x402 endpoint paid to your wallet with one signature, on every host, so your name, website, contact and docs show next to them (plus a 10-day Seller Watch trial). Use when: you operate x402 endpoints. Not for: buyers or third parties; only the payTo wallet can sign. Flow: call with wallet and profile to get message_to_sign and issued_at; sign with that wallet; call again with issued_at and signature. action=remove withdraws a claim (reversible by claiming again). Claims never change scores.

Input Schema

Name	Required	Description
`docs`	No	Your API documentation, as a full https URL
`name`	No	Seller name to show on your endpoints, up to 80 characters, e.g. Acme Data
`action`	No	claim (default) or remove to withdraw an existing claim
`wallet`	Yes	The payTo wallet your endpoints are paid to: 0x + 40 hex characters on Base, or a base58 address on Solana
`contact`	No	How buyers can reach you, e.g. hello@example.com or @handle on X
`website`	No	Your website, as a full https URL
`issued_at`	No	The issued_at timestamp returned by the first call; send it back unchanged with the signature
`signature`	No	Signature of message_to_sign by the wallet: EIP-191 personal_sign (0x hex) on Base, ed25519 (base58) on Solana; omit on the first call

Output Schema

Name	Required	Description
`note`	No	What the claim does
`error`	No	signature_required on the first call (sign message_to_sign and call again), or why the claim was refused
`covers`	No	The endpoints and hosts the claim covers
`wallet`	No	The wallet
`claimed`	No	true once the claim is recorded
`network`	No	The wallet's network
`profile`	No	The published profile: name, website, contact, docs
`removed`	No	true once a claim is withdrawn
`issued_at`	No	Timestamp to send back with the signature
`attestation`	No	EIP-191 signature over the answer; verify it with settled_verify or any EVM library
`attested_at`	No	When Settled signed this answer (ISO 8601)
`would_cover`	No	The endpoints and hosts the claim would cover
`message_to_sign`	No	The exact message to sign with the wallet

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedOct 5, 2026

changedInput schema / properties / contact / description

Previous value: -"How buyers can reach you, e.g. an email address or X handle"New value: +"How buyers can reach you, e.g. hello@example.com or @handle on X"

addedInput schema / properties / contact / maxLength
```
Added value: +120
```

changedInput schema / properties / docs / description

Previous value: -"URL of your API documentation"New value: +"Your API documentation, as a full https URL"

addedInput schema / properties / docs / format
```
Added value: +"uri"
```

changedInput schema / properties / issued_at / description

Previous value: -"The issued_at returned by the first call; send it back with the signature"New value: +"The issued_at timestamp returned by the first call; send it back unchanged with the signature"

changedInput schema / properties / name / description

Previous value: -"Seller name to show on your endpoints"New value: +"Seller name to show on your endpoints, up to 80 characters, e.g. Acme Data"

addedInput schema / properties / name / maxLength
```
Added value: +80
```

changedInput schema / properties / signature / description

Previous value: -"Signature of message_to_sign by the wallet: EIP-191 personal_sign on Base, ed25519 on Solana"New value: +"Signature of message_to_sign by the wallet: EIP-191 personal_sign (0x hex) on Base, ed25519 (base58) on Solana; omit on the first call"

changedInput schema / properties / wallet / description

Previous value: -"The payTo wallet your endpoints are paid to (0x... on Base, base58 on Solana)"New value: +"The payTo wallet your endpoints are paid to: 0x + 40 hex characters on Base, or a base58 address on Solana"

addedInput schema / properties / wallet / maxLength
```
Added value: +64
```
addedInput schema / properties / wallet / minLength
```
Added value: +32
```

changedInput schema / properties / website / description

Previous value: -"Your website URL"New value: +"Your website, as a full https URL"

addedInput schema / properties / website / format
```
Added value: +"uri"
```

First observedOct 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare the write/idempotent/non-destructive profile, and the description adds substantial context on top: it is free, requires a two-step sign-then-submit flow, only the payTo wallet may sign, action=remove is reversible by re-claiming, and claims never change scores. That covers cost, auth, side effects, and an important non-effect.

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

Conciseness5/5

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

Front-loaded with audience and value, then use/not-for, then the flow, then the remove caveat. Dense but every clause (cost, signature flow, reversibility, score neutrality) carries information an agent needs.

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 an 8-parameter, annotated, write tool with an output schema, the description covers audience, precondition, two-step flow, cost, and removal semantics. Return values are covered by the output schema, so nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the individual fields are already documented. The description adds cross-parameter semantics the schema cannot convey: the ordering between wallet/profile, message_to_sign/issued_at, and signature across two calls, plus the action=remove behavior. It stops short of deeper per-parameter detail, which the schema already owns.

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?

States a specific verb (claim) and resource (x402 endpoints paid to your wallet), and names the audience (sellers). It is clearly distinguishable from siblings like settled_check, settled_watch, and settled_income_* which serve different purposes.

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

Usage Guidelines5/5

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

Explicit 'Use when: you operate x402 endpoints' and 'Not for: buyers or third parties; only the payTo wallet can sign,' giving both the trigger condition and the exclusions/precondition. This is textbook when/when-not guidance.

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

All Settled 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.

Resources

Need Help?