Servidor MCP
GreenlandAI
ai.greenlandai/greenlandai
Qué hace este MCP
Provides a company graph and map, an agent marketplace, wallets, and on-chain verification features.
Capacidades
Herramientas
37
herramientas
balance_proof
Cryptographic inclusion proof for YOUR wallet balance in the latest hourly transparency
attestation (GET /wallet/balance-proof): leaf hash, Merkle sibling path, root, the anchoring BSV
txid, and `verification` (the steps to recompute the root and check it on chain). Bearer required;
the wallet is the one your credential owns — there is NO wallet_id argument, the backend resolves it
from your token. Anchoring is batched exactly like transparency_latest: `bsv_txid` may read "pending"
until this attestation's OP_RETURN batch (five per transaction, roughly every five hours) is
broadcast — not-yet-batched is not unanchored; for the most recent anchored root read
transparency_latest.last_anchored.
Esquema de entrada
{'type': 'object', 'title': 'balance_proofArguments', 'properties': {}}
Esquema de salida
{'type': 'object', 'title': 'balance_proofDictOutput', 'additionalProperties': True}
billing_attempts
YOUR OWN CHARGE RECORD — what this wallet was charged for, attempt by attempt, so you can verify your
bill without asking us (relays GET /api/v1/billing/attempts; own wallet only — derived from your credential,
never a parameter). Distinct from `joules_balance` (how much I have): this answers WHAT I WAS CHARGED FOR.
Each item: `status` — pending = reserved, not yet settled · completed = settled; `settled_all_in_joules` left
the wallet (base + the 0.5% rail fee) · settled_zero = delivered nothing, nothing moved · failed = released,
nothing moved (a 4xx, a 5xx, a refused reservation) · settle_failed = delivered but unsettled — new queries
refuse until it clears · expired = past the 15-minute replay window, superseded · refunded = reversed in full.
`reserved_joules` vs `settled_joules` is the settle-for-delivered difference (partial hops, empty results).
Match `attempt_id` to `metering.attempt_id` in the response body you got (or the `X-Metering-Attempt` header /
`price.attempt_id`; `look_at`'s image result carries it as `metering_attempt`).
`limit` 1-200 (default 50), `offset` for paging. Bearer or agent key required.
Esquema de entrada
{'type': 'object', 'title': 'billing_attemptsArguments', 'properties': {'limit': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Limit', 'default': None}, 'offset': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Offset', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'AttemptsOut', 'properties': {'note': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Note', 'default': None}, 'count': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Count', 'default': None}, 'items': {'anyOf': [{'type': 'array', 'items': {}}, {'type': 'null'}], 'title': 'Items', 'default': None}, 'statuses': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Statuses', 'default': None}, 'wallet_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Wallet Id', 'default': None}}, 'description': "billing_attempts — the caller's own charge record (GET /api/v1/billing/attempts): items[] of\n{attempt_id, when, settled_at, endpoint, query_type, status, reserved_joules, settled_joules,\nsettled_all_in_joules, idempotency_key, transfer_id, detail} + count + wallet_id + a statuses legend.\nItems stay opaque (list[Any]) so a backend field this relay does not model passes through verbatim.", 'additionalProperties': True}
billing_quote
The exact per-caller price of a metered call BEFORE you make it — free, no website, an MCP tool you
can actually invoke (relays GET /api/v1/billing/quote). `path` = the API path the call would hit — e.g.
"/api/v1/relationships" (the `relationships` tool), "/api/v1/look.from" (`look_from`), "/api/v1/map.viewport"
(`map_viewport`), "/api/v1/companies/{id}" (`company`), "/api/v1/deposits" (`deposits`),
"/api/v1/deposits/{id}" (`deposit`), "/api/v1/nearby" (`nearby`); `hops` = graph depth for a relationships path
(an agent key goes to 10 hops — every agent is on one set of terms; a human session to 3). Priced for YOU. Read
`joules_all_in` — the TRUE debit (base `joules` + `rail_fee_joules`, the 0.5% rail surcharge); fund
that, not the base. Graph paths price per hop and refund unused/empty hops
(`refund_on_empty`/`quote_is_maximum`). Bearer required, but NO verification — an unverified caller may
still price a call.
Esquema de entrada
{'type': 'object', 'title': 'billing_quoteArguments', 'required': ['path'], 'properties': {'hops': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Hops', 'default': None}, 'path': {'type': 'string', 'title': 'Path'}}}
Esquema de salida
{'type': 'object', 'title': 'QuoteOut', 'properties': {'peg': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Peg', 'default': None}, 'usd': {'anyOf': [{'type': 'number'}, {'type': 'null'}], 'title': 'Usd', 'default': None}, 'hops': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Hops', 'default': None}, 'path': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Path', 'default': None}, 'joules': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Joules', 'default': None, 'description': 'BASE price, before the rail surcharge'}, 'query_type': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Query Type', 'default': None}, 'billed_hops': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Billed Hops', 'default': None}, 'pricing_tier': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Pricing Tier', 'default': None}, 'rate_per_hop': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Rate Per Hop', 'default': None}, 'joules_all_in': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Joules All In', 'default': None, 'description': 'THE TRUE DEBIT — fund this, not `joules`'}, 'pricing_model': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Pricing Model', 'default': None}, 'rail_fee_joules': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Rail Fee Joules', 'default': None, 'description': 'the ~0.5% rail surcharge, rounded up'}, 'refund_on_empty': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Refund On Empty', 'default': None}, 'quote_is_maximum': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Quote Is Maximum', 'default': None}, 'partial_refund_note': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Partial Refund Note', 'default': None}}, 'description': "billing_quote — covers BOTH backend shapes (pricing_model 'per_hop' carries billed_hops /\nrate_per_hop / refund_on_empty / quote_is_maximum; 'flat_query_type' omits them). All optional,\nso neither shape errors.", 'additionalProperties': True}
bridge_proof
Cryptographic inclusion proofs for YOUR Bridge Ledger rows — contribution/fee events — in the
balance-proof shape (GET /programme/bridge/proof): per-row leaf hash, sibling path, the `bridge_root`,
and the anchoring BSV txid, plus `verification`. Bearer required; scoped to the holder your token
resolves to — no argument. `anchoring` is either "anchored" (with a real 64-hex `bsv_txid`) or a
pending note: Bridge rows are anchored by being batched into the hourly transparency attestation
(five attestations per OP_RETURN transaction, roughly every five hours), so the newest rows read
pending until their batch is broadcast and then carry the batch txid. Nothing is computed on request
— it reads what the attestation stored.
Esquema de entrada
{'type': 'object', 'title': 'bridge_proofArguments', 'properties': {}}
Esquema de salida
{'type': 'object', 'title': 'bridge_proofDictOutput', 'additionalProperties': True}
company
One company's record and graph neighbourhood by id; the response carries `charged_joules` — the
all-in PRICE of THIS call (one key on every metered response — the companies/deposits/infrastructure/
projects reads, relationships, and look_from / map_viewport / look_at). Metered — debited from the CALLING
agent's own
wallet, not the owner's (read it with the `joules_balance` tool). For the exact per-caller price before
you call, use the `billing_quote` tool (free, tier-aware; returns `joules_all_in`) or check
affordability with the `joules_deficit` tool; the true debit is the base `joule_cost` plus a 0.5% rail
surcharge rounded up (a 100 J call debits 101 J) = `joules_all_in`.
⚠ CHARGING: the meter RESERVES before the query runs and SETTLES after delivery for what was actually
delivered (an empty result settles to 0; a partial traversal settles for the hops delivered; a 4xx
releases the reservation). An abandoned or timed-out call still settles once the backend delivers.
A replay is served free only for the SAME credential + SAME idempotency key + SAME request within
15 minutes — a different payer is a different payer. Every call through this relay carries a fresh
key, so a retry here is always a new charge. Price with `billing_quote` first; verify any charge
with the `billing_attempts` tool (own wallet: reserved vs settled, per attempt).
WHAT YOU PAID: the JSON response carries a top-level `charged_joules` — the all-in PRICE of this call —
and a `metering` block written AFTER the settle has run: {attempt_id, settlement, settled_joules, check}.
`metering.settlement` is whether you PAID: settled · settled_zero (empty result, nothing moved) ·
settle_failed (delivered but UNPAID — the wallet is then locked until it clears; the next metered call
402s naming the attempt, the amount and what clears it) · released (4xx/5xx, nothing moved) · unknown.
`settled_joules` is what actually left the wallet (0 unless settled). A cached replay carries no block.
Esquema de entrada
{'type': 'object', 'title': 'companyArguments', 'required': ['id'], 'properties': {'id': {'type': 'string', 'title': 'Id'}}}
Esquema de salida
{'type': 'object', 'title': 'companyDictOutput', 'additionalProperties': True}
contribute_receipts
Your OWN append-only contribution receipts (forward your enabled gai_ key as X-API-Key) — the
proof of what you submitted, with the canonical claim hash (claim_sha256) so you can verify what the
door holds matches what you sent. Own rows only, no staff fields. Read-only.
GET /api/v1/contribute/receipts.
Esquema de entrada
{'type': 'object', 'title': 'contribute_receiptsArguments', 'properties': {'limit': {'type': 'integer', 'title': 'Limit', 'default': 50}, 'offset': {'type': 'integer', 'title': 'Offset', 'default': 0}}}
Esquema de salida
{'type': 'object', 'title': 'contribute_receiptsDictOutput', 'additionalProperties': True}
contribute_relations
Submit evidenced graph relationships to the GreenlandAI contributor door (TEN programme). Auth:
your OWN GreenlandAI key in X-API-Key — an agent's gai_ registration key or the owner's gai_ key,
the SAME key you use on the graph reads; the agent ID (gqa_) is NOT sent here, the door derives your
contributor identity from the key. Contribute must first be enabled on that identity (a one-time
human action on greenlandai.ai; the door returns a 403 naming the enable endpoint if it is not).
Each item in `relations` MUST carry: subject, relation, object, source_url (a real http(s) page),
quote (a verbatim passage >= 15 chars from that page stating the relationship — the judge refutes
against it; a missing or placeholder source or quote is rejected at the door). Optional per item:
subject_type, object_type. `entities` (optional) proposes a NEW endpoint ONLY alongside a relation
that references it — a proposed entity is never accepted on its own. Nothing is written to the graph
on submit: admitted claims are QUEUED for the nightly refutation judge (21:15 UTC). Per-item
`results[].status`: queued_for_judgement / bundled_with_proposed_entity (queued) · duplicate /
already_pending (accepted, not re-counted) · unmapped_relation (vocabulary review, not counted) ·
unresolved_subject|object (endpoint not found — `suggestions` returned; not counted) · self_loop /
source_excluded / invalid (rejected, with reasons). The judge's verdict — promoted, HELD, or
dismissed, with its reason — then appears per item via the contribute_submissions tool; the receipt
via contribute_receipts; a HELD item is not a failure and is not counted until decided. Standing
weights, streams and thresholds are live at GET /api/v1/programme/config — not restated here.
Esquema de entrada
{'type': 'object', 'title': 'contribute_relationsArguments', 'required': ['relations'], 'properties': {'entities': {'anyOf': [{'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}}, {'type': 'null'}], 'title': 'Entities', 'default': None}, 'relations': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}, 'title': 'Relations'}}}
Esquema de salida
{'type': 'object', 'title': 'contribute_relationsDictOutput', 'additionalProperties': True}
contribute_stats
Your OWN contributor standing (forward your enabled gai_ key as X-API-Key; the door derives
identity from the key). Returns totals (submitted/accepted/rejected), acceptance_rate,
pending_review, refused_at_door, standing (good / warning / suspended / revoked) and the thresholds
that apply after a floor of submissions. Read-only. GET /api/v1/contribute/status.
Esquema de entrada
{'type': 'object', 'title': 'contribute_statsArguments', 'properties': {}}
Esquema de salida
{'type': 'object', 'title': 'contribute_statsDictOutput', 'additionalProperties': True}
contribute_submissions
Your OWN per-item submission outcomes (forward your enabled gai_ key as X-API-Key). Each item:
id, kind, name, outcome (pending_review / accepted / rejected), the judge's reason verbatim in
review_note (a pending item reads 'awaiting the judge (nightly, 21:15 UTC)'; a HELD item carries
the judge's reason), duplicate flag, promoted {table, id}?, bundle_id?, submitted_at. Read-only.
GET /api/v1/contribute/submissions.
Esquema de entrada
{'type': 'object', 'title': 'contribute_submissionsArguments', 'properties': {'limit': {'type': 'integer', 'title': 'Limit', 'default': 50}, 'offset': {'type': 'integer', 'title': 'Offset', 'default': 0}}}
Esquema de salida
{'type': 'object', 'title': 'contribute_submissionsDictOutput', 'additionalProperties': True}
deposit
One resource deposit's record by numeric id (relays GET /api/v1/deposits/{id}), including its
`commodities[]` ({name, role: primary|byproduct, group} — the commodity graph, with `resource_type`
as the primary label) and operators. Pair with `deposits(commodity=...)`: search by commodity,
then read the deposit. Metered — debited from the CALLING agent's own wallet; the response carries
`charged_joules` (the all-in PRICE of this call) and the `metering` block (`metering.settlement` = whether you
PAID, `settled_joules` = what left the wallet). Quote with `billing_quote("/api/v1/deposits/{id}")`.
Esquema de entrada
{'type': 'object', 'title': 'depositArguments', 'required': ['id'], 'properties': {'id': {'type': 'string', 'title': 'Id'}}}
Esquema de salida
{'type': 'object', 'title': 'depositDictOutput', 'additionalProperties': True}
deposits
Search resource deposits (relays GET /api/v1/deposits). Filters: `commodity`, `resource_type`,
`country`, `status`, `owner_country`, `max_port_km`, `search` (name substring), `limit` (<=100),
`offset`.
⚠ READ THIS BEFORE USING `commodity`: it filters by the commodity GRAPH, not by the deposit's
`resource_type` string. A deposit matches if it CONTAINS the commodity directly, OR CONTAINS a
commodity GROUP the commodity is MEMBER_OF. So `commodity="neodymium"` returns EVERY
rare-earth-element deposit — including ones whose name and `resource_type` never say "neodymium"
(they host the rare_earth_elements group, of which neodymium is a member). That is correct, not a
broken filter. The response's top-level `commodity_filter` {query, matched_directly,
matched_via_group} tells you which happened — `matched_via_group` names the group (e.g.
"rare_earth_elements") when the match came through it. Each deposit carries `commodities[]`
({name, role: primary|byproduct, group}); `resource_type` stays the primary label. Response shape:
{count, total, deposits[], commodity_filter, charged_joules, metering}. Metered — `charged_joules` is the
all-in PRICE of this call, debited from the CALLING agent's own wallet; `metering.settlement` /
`metering.settled_joules` say whether it was actually PAID (settled · settled_zero · settle_failed =
delivered but unpaid · released · unknown). Quote first with `billing_quote("/api/v1/deposits")`. Same as the
SDK `deposits(commodity=...)`.
Esquema de entrada
{'type': 'object', 'title': 'depositsArguments', 'properties': {'limit': {'type': 'integer', 'title': 'Limit', 'default': 50}, 'offset': {'type': 'integer', 'title': 'Offset', 'default': 0}, 'search': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Search', 'default': None}, 'status': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Status', 'default': None}, 'country': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Country', 'default': None}, 'commodity': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Commodity', 'default': None}, 'max_port_km': {'anyOf': [{'type': 'number'}, {'type': 'null'}], 'title': 'Max Port Km', 'default': None}, 'owner_country': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Owner Country', 'default': None}, 'resource_type': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Resource Type', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'depositsDictOutput', 'additionalProperties': True}
deposit_status
YOUR OWN USDC-on-Base deposit state (relays GET /api/v1/wallet/deposit-status; own wallet only,
derived from your credential, never a parameter). States: credited (joules in your wallet) ·
held_below_min (under `minimum_usdc` — held and accumulated, credits as one entry once your total
reaches it; nothing lost) · held_above_max (over the max — held for a human to release; nothing lost) ·
swept · held_no_fund (the deposit reached the minimum but the platform's funding wallet could not cover the joules at that moment — held, nothing moved, nothing lost; credited AUTOMATICALLY once platform funding is restored — the scanner retries it every minute — no action needed from you). Sent USDC and see nothing yet? Compare your deposit's Base block to
scanner_cursor_block: above it = normal lag (the scanner hasn't reached it); at/below it with no row =
flagged, not lost. held_below_min / held_above_max / swept / held_no_fund have not yet occurred on real
funds. held_inactive (the wallet was not active — closed or frozen — when the deposit arrived; held, nothing
credited, released by an operator once it is active again). Bearer or agent key required. A GreenlandAI AGENT key
(gai_) reads its own wallet's deposits (greenlandai.ai/api/v1/agent/me/deposit-status); an owner's developer key is
told where its own address and status are.
Esquema de entrada
{'type': 'object', 'title': 'deposit_statusArguments', 'properties': {}}
Esquema de salida
{'type': 'object', 'title': 'DepositStatusOut', 'properties': {'note': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Note', 'default': None}, 'deposits': {'anyOf': [{'type': 'array', 'items': {}}, {'type': 'null'}], 'title': 'Deposits', 'default': None}, 'usdc_live': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Usdc Live', 'default': None}, 'minimum_usdc': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Minimum Usdc', 'default': None}, 'scanner_cursor_block': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Scanner Cursor Block', 'default': None}, 'needed_to_credit_usdc': {'anyOf': [{}, {'type': 'null'}], 'title': 'Needed To Credit Usdc', 'default': None}, 'held_below_min_total_usdc': {'anyOf': [{}, {'type': 'null'}], 'title': 'Held Below Min Total Usdc', 'default': None}}, 'description': 'deposit_status — relayed verbatim from GET /api/v1/wallet/deposit-status (extra fields pass through).', 'additionalProperties': True}
funding_prepare
The in-band funding step for a joule shortfall — NEVER a website to visit (operator lock). USDC on
Base is the live agent-fundable rail: deposit USDC to your own Base address (derived from your
credential), at or above the live minimum (`minimum_usdc`, read per call from deposit-status), credited
automatically when the deposit scanner sees it — track it with `deposit_status`. Card funding stays a human web flow. Availability is read from the running system per
call (relays your deposit-address), so this never reports stale state; it does not itself move money. A
GreenlandAI AGENT key (gai_) gets its OWN USDC address (greenlandai.ai/api/v1/agent/me/deposit-address — credits the
agent's own wallet) plus its owner's funding route; an owner's developer key is told where its own address is.
Esquema de entrada
{'type': 'object', 'title': 'funding_prepareArguments', 'properties': {'needed': {'type': 'integer', 'title': 'Needed', 'default': 0}}}
Esquema de salida
{'type': 'object', 'title': 'FundingPrepareOut', 'properties': {'note': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Note', 'default': None}, 'needed': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Needed', 'default': None}, 'routes': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Routes', 'default': None}, 'wallet_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Wallet Id', 'default': None}, 'in_band_agent_funding_live': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'In Band Agent Funding Live', 'default': None}}, 'description': "funding_prepare — relays deposit-address for live USDC availability + the caller's own address.", 'additionalProperties': True}
hops
DEPRECATED alias for `relationships` — kept working, to be removed at a future major. Use
`relationships`. Reason (operator ruling 2026-09-14): `hops` names the tool after the BILLING UNIT
(traversal depth is what we meter, and `billing_quote` takes hops= for that reason), but the
capability is the relationship EDGES with tiers + provenance — a tool list should name the capability,
not the meter. Identical behavior and params to `relationships` (incl. an unknown `relation_type` = 400 on
both paths, before any charge); also the SDK helper name.
⚠ CHARGING: the meter RESERVES before the query runs and SETTLES after delivery for what was actually
delivered (an empty result settles to 0; a partial traversal settles for the hops delivered; a 4xx
releases the reservation). An abandoned or timed-out call still settles once the backend delivers.
A replay is served free only for the SAME credential + SAME idempotency key + SAME request within
15 minutes — a different payer is a different payer. Every call through this relay carries a fresh
key, so a retry here is always a new charge. Price with `billing_quote` first; verify any charge
with the `billing_attempts` tool (own wallet: reserved vs settled, per attempt).
WHAT YOU PAID: the JSON response carries a top-level `charged_joules` — the all-in PRICE of this call —
and a `metering` block written AFTER the settle has run: {attempt_id, settlement, settled_joules, check}.
`metering.settlement` is whether you PAID: settled · settled_zero (empty result, nothing moved) ·
settle_failed (delivered but UNPAID — the wallet is then locked until it clears; the next metered call
402s naming the attempt, the amount and what clears it) · released (4xx/5xx, nothing moved) · unknown.
`settled_joules` is what actually left the wallet (0 unless settled). A cached replay carries no block.
Esquema de entrada
{'type': 'object', 'title': 'hopsArguments', 'properties': {'hops': {'type': 'integer', 'title': 'Hops', 'default': 1}, 'limit': {'type': 'integer', 'title': 'Limit', 'default': 50}, 'entity': {'type': 'string', 'title': 'Entity', 'default': None}, 'offset': {'type': 'integer', 'title': 'Offset', 'default': 0}, 'search': {'type': 'string', 'title': 'Search', 'default': None}, 'relation_type': {'type': 'string', 'title': 'Relation Type', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'hopsDictOutput', 'additionalProperties': True}
joules_balance
Your own wallet balance — a FREE read either way (checking costs nothing). A GreenlandAI AGENT key
(`gai_`/`gqa_`) reads its OWN wallet via GAI /api/v1/agent/me/balance — NO wallet_id needed; returns
{agent_id, agent_name, wallet_id, balance_joules, balance}. A JoulePAI (`jlp_`) or ENYAL (`eyl_`)
credential reads by `wallet_id` via JoulePAI /wallet/balance and returns {balance, wallet_id, …}. (The
graph/map meter debits this same wallet — this is how an agent checks it before calling.)
Esquema de entrada
{'type': 'object', 'title': 'joules_balanceArguments', 'properties': {'wallet_id': {'type': 'string', 'title': 'Wallet Id', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'BalanceOut', 'properties': {'id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Id', 'default': None, 'description': 'JoulePAI branch returns the wallet id here'}, 'handle': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Handle', 'default': None}, 'balance': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Balance', 'default': None, 'description': 'spendable joules; the field to act on'}, 'agent_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Agent Id', 'default': None}, 'wallet_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Wallet Id', 'default': None}, 'agent_name': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Agent Name', 'default': None}, 'owner_type': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Owner Type', 'default': None}, 'balance_joules': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Balance Joules', 'default': None, 'description': 'GAI agent-branch name for the same figure'}, 'verification_status': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Verification Status', 'default': None}}, 'description': 'joules_balance — the union of its two branches. GAI agent-key branch returns\n{agent_id, agent_name, wallet_id, balance_joules} (+ the `balance` shape-compat shim added by\nthis relay); the JoulePAI branch returns WalletOut, whose wallet id field is `id`, not\n`wallet_id`. Both are declared so either branch is structured. PII the JP branch may carry\n(email, bsv_address, signup_grant) is deliberately NOT declared — it still passes through as an\nextra, but it is not advertised in a schema that anonymous clients can enumerate.', 'additionalProperties': True}
joules_deficit
Given a planned `cost`, read a balance and return {needed, have, shortfall, tool_to_call_next} so an
agent can decide in-band whether it can afford the next call — no website, no guessing, FREE. A
GreenlandAI AGENT key (`gai_`/`gqa_`) reads its OWN balance via GAI /api/v1/agent/me/balance (no
wallet_id). A JoulePAI/ENYAL credential reads via JoulePAI — `wallet_id` OPTIONAL (omit → resolved via
/wallet/me), pass it for a specific wallet.
Esquema de entrada
{'type': 'object', 'title': 'joules_deficitArguments', 'required': ['cost'], 'properties': {'cost': {'type': 'integer', 'title': 'Cost'}, 'wallet_id': {'type': 'string', 'title': 'Wallet Id', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'DeficitOut', 'properties': {'have': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Have', 'default': None}, 'needed': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Needed', 'default': None}, 'shortfall': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Shortfall', 'default': None, 'description': '0 means affordable now'}, 'tool_to_call_next': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Tool To Call Next', 'default': None, 'description': 'null when nothing is owed'}}, 'description': 'joules_deficit — computed by this relay, not relayed.', 'additionalProperties': True}
ledger_verify
Recent public ledger anchors with their on-chain transaction ids and the exact credit supply at
each anchor — public, no auth. Independently checkable.
Esquema de entrada
{'type': 'object', 'title': 'ledger_verifyArguments', 'properties': {}}
Esquema de salida
{'type': 'object', 'title': 'LedgerVerifyOut', 'properties': {'eras': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Eras', 'default': None}, 'total': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Total', 'default': None}, 'anchors': {'anyOf': [{'type': 'array', 'items': {}}, {'type': 'null'}], 'title': 'Anchors', 'default': None}, 'coverage': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Coverage', 'default': None}, 'hash_format': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Hash Format', 'default': None}, 'chain_semantics': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Chain Semantics', 'default': None}}, 'description': 'ledger_verify — public anchor list. `anchors` left opaque (per-anchor records).', 'additionalProperties': True}
look_at
Satellite still of a place — a Sentinel-2 ARCHIVE image (the screen as a picture). Pose = lat/lng OR
entity_type+id (anchor); same pose family as `look_from`. Optional `as_of` (YYYY-MM-DD — the newest
scene on/before that date) and `max_cloud` (0-100, default 20). AGENT KEYS ONLY (a session/dev key is
refused BEFORE any charge). Metered on its own price line — quote it first with
`billing_quote("/api/v1/look.at")` — and refunded in full if no image is delivered. RETURNS THE IMAGE (jpeg) as MCP image content PLUS `structuredContent` provenance from the
scene's headers — read these and claim nothing stronger: `observed_at` is the SCENE's date, NEVER the
request's; `source_tier` is the PROVIDER's, never the pin's; `freshness` is "archive", never "live";
plus cloud_cover, gsd, extent_km, attribution, cache, entity_cap_consumed (0), and the charge:
`price_charged_joules` (the all-in price) + `metering_attempt` / `metering_status` — the settle truth for an
IMAGE, which has no JSON body to carry a `metering` block (the X-Metering-Status header: completed = paid ·
settled_zero · settle_failed = delivered but UNPAID · released · cached_replay). A cloudy or
MISSING scene returns `available:false` + `freshness:"unavailable"` and is REFUNDED IN FULL — an
unavailable RESULT, not an error, and NEVER a fabricated image; that JSON carries top-level `charged_joules`
(0 — refunded) and the `metering` block described below.
⚠ CHARGING: the meter RESERVES before the query runs and SETTLES after delivery for what was actually
delivered (an empty result settles to 0; a partial traversal settles for the hops delivered; a 4xx
releases the reservation). An abandoned or timed-out call still settles once the backend delivers.
A replay is served free only for the SAME credential + SAME idempotency key + SAME request within
15 minutes — a different payer is a different payer. Every call through this relay carries a fresh
key, so a retry here is always a new charge. Price with `billing_quote` first; verify any charge
with the `billing_attempts` tool (own wallet: reserved vs settled, per attempt).
WHAT YOU PAID: the JSON response carries a top-level `charged_joules` — the all-in PRICE of this call —
and a `metering` block written AFTER the settle has run: {attempt_id, settlement, settled_joules, check}.
`metering.settlement` is whether you PAID: settled · settled_zero (empty result, nothing moved) ·
settle_failed (delivered but UNPAID — the wallet is then locked until it clears; the next metered call
402s naming the attempt, the amount and what clears it) · released (4xx/5xx, nothing moved) · unknown.
`settled_joules` is what actually left the wallet (0 unless settled). A cached replay carries no block.
Esquema de entrada
{'type': 'object', 'title': 'look_atArguments', 'properties': {'id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Id', 'default': None}, 'lat': {'anyOf': [{'type': 'number'}, {'type': 'null'}], 'title': 'Lat', 'default': None}, 'lng': {'anyOf': [{'type': 'number'}, {'type': 'null'}], 'title': 'Lng', 'default': None}, 'as_of': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'As Of', 'default': None}, 'max_cloud': {'type': 'number', 'title': 'Max Cloud', 'default': 20.0}, 'entity_type': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Entity Type', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'look_atDictOutput', 'additionalProperties': True}
look_from
Map lane: pins near a point (lat/lng + radius_km). `entity_type` (deposit | infrastructure | company
| project) behaves two ways (backend, 2026-09-14): `entity_type` ALONE (with lat/lng) FILTERS the frame
to that type only; `entity_type` + `id` ANCHORS the pose at that entity and keeps ALL types; an unknown
`entity_type` is a 400 BEFORE any charge (wallet unmoved). Metered — debited from the CALLING agent's own
wallet, not the owner's; the response's top-level `charged_joules` is the ALL-IN price (base + 0.5% rail —
the same figure as `price.charged_joules`; the `price` block stays as the breakdown). Read the
wallet with the `joules_balance` tool. For the exact per-caller price before you call, use the `billing_quote` tool
(free, tier-aware; returns `joules_all_in`) or check affordability with the `joules_deficit` tool; the
true debit is the base `joule_cost` plus a 0.5% rail surcharge rounded up (a 100 J call debits 101 J) =
`joules_all_in`. Results carry `source_tier`/`tier_label` per pin — provenance you
should keep. They reflect the pin at read time; a pin's tier or an edge in its `operators` can change
afterwards and a held result will not reflect that. `energy=true` includes energy fleet infra;
`include_country_centroids=true` adds country-centroid placeholder pins (both off by default).
⚠ CHARGING: the meter RESERVES before the query runs and SETTLES after delivery for what was actually
delivered (an empty result settles to 0; a partial traversal settles for the hops delivered; a 4xx
releases the reservation). An abandoned or timed-out call still settles once the backend delivers.
A replay is served free only for the SAME credential + SAME idempotency key + SAME request within
15 minutes — a different payer is a different payer. Every call through this relay carries a fresh
key, so a retry here is always a new charge. Price with `billing_quote` first; verify any charge
with the `billing_attempts` tool (own wallet: reserved vs settled, per attempt).
WHAT YOU PAID: the JSON response carries a top-level `charged_joules` — the all-in PRICE of this call —
and a `metering` block written AFTER the settle has run: {attempt_id, settlement, settled_joules, check}.
`metering.settlement` is whether you PAID: settled · settled_zero (empty result, nothing moved) ·
settle_failed (delivered but UNPAID — the wallet is then locked until it clears; the next metered call
402s naming the attempt, the amount and what clears it) · released (4xx/5xx, nothing moved) · unknown.
`settled_joules` is what actually left the wallet (0 unless settled). A cached replay carries no block.
Esquema de entrada
{'type': 'object', 'title': 'look_fromArguments', 'properties': {'id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Id', 'default': None}, 'lat': {'anyOf': [{'type': 'number'}, {'type': 'null'}], 'title': 'Lat', 'default': None}, 'lng': {'anyOf': [{'type': 'number'}, {'type': 'null'}], 'title': 'Lng', 'default': None}, 'energy': {'type': 'boolean', 'title': 'Energy', 'default': False}, 'radius_km': {'type': 'number', 'title': 'Radius Km', 'default': 100}, 'entity_type': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Entity Type', 'default': None}, 'include_country_centroids': {'type': 'boolean', 'title': 'Include Country Centroids', 'default': False}}}
Esquema de salida
{'type': 'object', 'title': 'look_fromDictOutput', 'additionalProperties': True}
mapdata
CLOSED — do NOT call. `/api/v1/mapdata` (the bulk map-layers surface) is TEMPORARILY closed to ALL
callers, agent AND human: the backend returns 403 BEFORE the meter, so NOTHING is charged (GR-109
operator ruling 2026-09-08, gated on AGENT_MAPDATA_ENABLED / HUMAN_MAPDATA_ENABLED — both default off
while the map moves to a viewport surface). USE INSTEAD: `map_viewport` for a bounding box (capped pins
+ counts_by_type) or `look_from` for a pose (pins near a point or anchored on an entity). Kept in the
tool list (not removed) so an enumerated list stays stable; reopens metered if the flags flip. (When
open it was: metered map dataset, layers + include_country_centroids.)
Esquema de entrada
{'type': 'object', 'title': 'mapdataArguments', 'properties': {'layers': {'type': 'string', 'title': 'Layers', 'default': 'companies'}, 'include_country_centroids': {'type': 'boolean', 'title': 'Include Country Centroids', 'default': False}}}
Esquema de salida
{'type': 'object', 'title': 'mapdataDictOutput', 'additionalProperties': True}
map_viewport
Map lane: everything inside a bounding box — THE SCREEN (relays GET /api/v1/map.viewport). Typed
params: min_lat/min_lng/max_lat/max_lng (the bbox — all four together), entity_type
(deposit | infrastructure | company | project — default all four), energy (default False; omits energy
fleet infra/projects), include_country_centroids (default False). Returns capped, id-ordered `pins`
plus `counts_by_type` — the counts are the TRUE totals for the whole bbox, the pins are a sample, so
read counts for totals and pins for detail. AGENT KEYS ONLY (a non-agent credential is refused BEFORE
any charge); a per-owner viewport rate window applies; pins do NOT count against your entity cap.
Metered — debited from the CALLING agent's own wallet (read it with the `joules_balance` tool); ONE
`basic` price per call; quote it with the `billing_quote` tool and the true debit is base + 0.5% rail
surcharge = `joules_all_in`. The response carries top-level `charged_joules` (the all-in price — the same
figure as `price.charged_joules`; the `price` block stays as the breakdown). Carries `source_tier`/`tier_label`
per pin; energy off, pipelines never,
centroids off unless asked (same honesty as `look_from`).
⚠ CHARGING: the meter RESERVES before the query runs and SETTLES after delivery for what was actually
delivered (an empty result settles to 0; a partial traversal settles for the hops delivered; a 4xx
releases the reservation). An abandoned or timed-out call still settles once the backend delivers.
A replay is served free only for the SAME credential + SAME idempotency key + SAME request within
15 minutes — a different payer is a different payer. Every call through this relay carries a fresh
key, so a retry here is always a new charge. Price with `billing_quote` first; verify any charge
with the `billing_attempts` tool (own wallet: reserved vs settled, per attempt).
WHAT YOU PAID: the JSON response carries a top-level `charged_joules` — the all-in PRICE of this call —
and a `metering` block written AFTER the settle has run: {attempt_id, settlement, settled_joules, check}.
`metering.settlement` is whether you PAID: settled · settled_zero (empty result, nothing moved) ·
settle_failed (delivered but UNPAID — the wallet is then locked until it clears; the next metered call
402s naming the attempt, the amount and what clears it) · released (4xx/5xx, nothing moved) · unknown.
`settled_joules` is what actually left the wallet (0 unless settled). A cached replay carries no block.
Esquema de entrada
{'type': 'object', 'title': 'map_viewportArguments', 'properties': {'energy': {'type': 'boolean', 'title': 'Energy', 'default': False}, 'max_lat': {'anyOf': [{'type': 'number'}, {'type': 'null'}], 'title': 'Max Lat', 'default': None}, 'max_lng': {'anyOf': [{'type': 'number'}, {'type': 'null'}], 'title': 'Max Lng', 'default': None}, 'min_lat': {'anyOf': [{'type': 'number'}, {'type': 'null'}], 'title': 'Min Lat', 'default': None}, 'min_lng': {'anyOf': [{'type': 'number'}, {'type': 'null'}], 'title': 'Min Lng', 'default': None}, 'entity_type': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Entity Type', 'default': None}, 'include_country_centroids': {'type': 'boolean', 'title': 'Include Country Centroids', 'default': False}}}
Esquema de salida
{'type': 'object', 'title': 'map_viewportDictOutput', 'additionalProperties': True}
market_accept
Accept a delivery on a match (POST /match/{id}/accept) — releases escrow to the provider. You
must be the buyer party; backend enforces it.
Esquema de entrada
{'type': 'object', 'title': 'market_acceptArguments', 'required': ['match_id'], 'properties': {'match_id': {'type': 'string', 'title': 'Match Id'}, 'idempotency_key': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Idempotency Key', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'market_acceptDictOutput', 'additionalProperties': True}
market_listings
Browse the RAREEAI marketplace: kind="providers" (listings) or "oracles". Typed query params for
the providers browse (GET /providers): frontier, resource_type, oracle_verified, active (default
True), limit (<=200, default 50), offset, sort (default "price_asc"). Needs a bearer; no write scope
to read.
Esquema de entrada
{'type': 'object', 'title': 'market_listingsArguments', 'properties': {'kind': {'type': 'string', 'title': 'Kind', 'default': 'providers'}, 'sort': {'type': 'string', 'title': 'Sort', 'default': 'price_asc'}, 'limit': {'type': 'integer', 'title': 'Limit', 'default': 50}, 'active': {'type': 'boolean', 'title': 'Active', 'default': True}, 'offset': {'type': 'integer', 'title': 'Offset', 'default': 0}, 'frontier': {'type': 'string', 'title': 'Frontier', 'default': None}, 'resource_type': {'type': 'string', 'title': 'Resource Type', 'default': None}, 'oracle_verified': {'type': 'boolean', 'title': 'Oracle Verified', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'market_listingsDictOutput', 'additionalProperties': True}
market_match
Read one marketplace match by id, including its `escrow_terms` and this trade's typed fee/timeout
fields. You must be a party to the match. Bearer required. `dispute_window_end` is populated on
oracle-path trades (a real timestamp, not null) — it is the deadline to open a dispute after
delivery; for the whole trade's settlement legs use `trade_settlement`.
Esquema de entrada
{'type': 'object', 'title': 'market_matchArguments', 'required': ['match_id'], 'properties': {'match_id': {'type': 'string', 'title': 'Match Id'}}}
Esquema de salida
{'type': 'object', 'title': 'market_matchDictOutput', 'additionalProperties': True}
market_provide
Create/update a marketplace listing (POST /provide). Requires marketplace:write (verified
account) — an unverified/under-scoped token gets the backend's real 403. First-time provider
registration charges a 1,000-joule fee that is SPENT (not a refundable stake — contrast an oracle
stake, which is returned on deregister). Body (TYPED — extra fields refused here): {wallet_id, frontier,
resource_type, unit_type, price_joules_per_unit (int >=0), capacity_total?, min_units?,
max_units_per_match?, endpoint_url?, sla? (dict), speed?, timeout_hours? / timeout_minutes?,
stake_amount?, oracle_verified? (opt in to oracle checks), idempotency_key?}.
Esquema de entrada
{'type': 'object', '$defs': {'ProvideBody': {'type': 'object', 'title': 'ProvideBody', 'required': ['wallet_id', 'frontier', 'resource_type', 'unit_type', 'price_joules_per_unit'], 'properties': {'sla': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Sla', 'default': None}, 'speed': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Speed', 'default': None}, 'frontier': {'type': 'string', 'title': 'Frontier'}, 'min_units': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Min Units', 'default': None}, 'unit_type': {'type': 'string', 'title': 'Unit Type'}, 'wallet_id': {'type': 'string', 'title': 'Wallet Id'}, 'endpoint_url': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Endpoint Url', 'default': None}, 'stake_amount': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Stake Amount', 'default': None}, 'resource_type': {'type': 'string', 'title': 'Resource Type'}, 'timeout_hours': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Timeout Hours', 'default': None}, 'capacity_total': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Capacity Total', 'default': None}, 'idempotency_key': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Idempotency Key', 'default': None}, 'oracle_verified': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Oracle Verified', 'default': None, 'description': 'opt IN to oracle verification of your deliveries (a preference, not a badge)'}, 'timeout_minutes': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Timeout Minutes', 'default': None}, 'max_units_per_match': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Max Units Per Match', 'default': None}, 'price_joules_per_unit': {'type': 'integer', 'title': 'Price Joules Per Unit', 'minimum': 0}}, 'additionalProperties': False}}, 'title': 'market_provideArguments', 'required': ['body'], 'properties': {'body': {'$ref': '#/$defs/ProvideBody'}}}
Esquema de salida
{'type': 'object', 'title': 'market_provideDictOutput', 'additionalProperties': True}
market_quote
Read one marketplace REQUEST by id (GET /request/{id}; you must own it). Returns the request as the
route actually declares it: id, wallet_id, agent_id, frontier, resource_type, unit_type, speed,
privacy_mode, contract_escrow, units_needed, max_price_per_unit, priority, requirements, status,
units_matched, expires_at, created_at, plus `escrow_terms` — a GENERIC prose block of the escrow rules,
identical on every request. It does NOT carry this trade's own figures: `fee_joules`,
`escrow_expires_at` and `dispute_window_end` are fields of the MATCH, so read them with `market_match`
once a match exists; `buyer_debit_joules` appears only on an x402 price quote (a 402 body). Bearer
required.
Esquema de entrada
{'type': 'object', 'title': 'market_quoteArguments', 'required': ['request_id'], 'properties': {'request_id': {'type': 'string', 'title': 'Request Id'}}}
Esquema de salida
{'type': 'object', 'title': 'RequestQuoteOut', 'properties': {'id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Id', 'default': None}, 'speed': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Speed', 'default': None}, 'status': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Status', 'default': None}, 'agent_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Agent Id', 'default': None}, 'frontier': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Frontier', 'default': None}, 'priority': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Priority', 'default': None}, 'unit_type': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Unit Type', 'default': None}, 'wallet_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Wallet Id', 'default': None}, 'created_at': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Created At', 'default': None}, 'expires_at': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Expires At', 'default': None}, 'escrow_terms': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Escrow Terms', 'default': None, 'description': 'generic escrow prose; opaque by design'}, 'privacy_mode': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Privacy Mode', 'default': None}, 'requirements': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Requirements', 'default': None}, 'units_needed': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Units Needed', 'default': None}, 'resource_type': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Resource Type', 'default': None}, 'units_matched': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Units Matched', 'default': None}, 'contract_escrow': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Contract Escrow', 'default': None}, 'max_price_per_unit': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Max Price Per Unit', 'default': None}}, 'description': "market_quote — RAREEAI RequestOut as the route actually declares it. `escrow_terms` is left\nOPAQUE on purpose: a GENERIC prose block, identical on every request. This trade's own figures\n(fee_joules, escrow_expires_at, dispute_window_end) live on MatchOut — the `market_match` payload —\nand are not on this route, so they are not declared here (the tool docstring now says the same).", 'additionalProperties': True}
market_request
Post a marketplace BUY request (POST /request) — you want to buy a resource; providers match against
it and your escrow is debited on match. Bearer + a verified account (marketplace:write); an
under-scoped token gets the backend's real 403. Body (TYPED — extra fields refused here):
{wallet_id (a UUID you own, pays escrow), frontier, resource_type, unit_type, units_needed (int >0),
max_price_per_unit (int >0, joules), priority?, requirements? (dict), ttl_seconds? (expiry), speed?,
privacy_mode?, contract_escrow?, idempotency_key?}. Quote a specific request with `market_quote` before
accepting a match.
ESCROW LANE: every trade's joules are held in escrow either way. The DEFAULT is the LEDGER LANE — escrow
held in a system wallet and settled on the ledger (each settlement leg anchored on chain), NO on-chain
contract and no contract fee; the match reads `escrow_bsv_state: "NO_CONTRACT"`, which is the normal,
terminal state of that lane, not a failure. Set `contract_escrow: true` to opt in to the on-chain escrow
contract lane for a flat contract fee added to your lock; the contract is mandatory for large trades.
It takes effect ONLY where an oracle backs the trade (large enough to attract oracle verification, or an
oracle-verified provider): a non-oracle opt-in falls back to the ledger lane with no contract and no fee,
and the match returns `contract_escrow: false` plus a `contract_note` saying why. Fee and thresholds:
https://raree.ai/llms.txt (not restated here). After settlement, `trade_settlement` shows the contract's
own legs in its `contract` section (null on a ledger-lane trade).
Esquema de entrada
{'type': 'object', '$defs': {'RequestBody': {'type': 'object', 'title': 'RequestBody', 'required': ['wallet_id', 'frontier', 'resource_type', 'unit_type', 'units_needed', 'max_price_per_unit'], 'properties': {'speed': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Speed', 'default': None}, 'frontier': {'type': 'string', 'title': 'Frontier'}, 'priority': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Priority', 'default': None}, 'unit_type': {'type': 'string', 'title': 'Unit Type'}, 'wallet_id': {'type': 'string', 'title': 'Wallet Id'}, 'ttl_seconds': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Ttl Seconds', 'default': None}, 'privacy_mode': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Privacy Mode', 'default': None}, 'requirements': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Requirements', 'default': None}, 'units_needed': {'type': 'integer', 'title': 'Units Needed', 'exclusiveMinimum': 0}, 'resource_type': {'type': 'string', 'title': 'Resource Type'}, 'contract_escrow': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Contract Escrow', 'default': None, 'description': 'opt in to the on-chain escrow contract lane (a flat contract fee added to your lock). Takes effect ONLY where an oracle backs the trade; otherwise the trade falls to the default ledger lane with no contract and no contract fee, and the match says why (contract_escrow=false + contract_note)'}, 'idempotency_key': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Idempotency Key', 'default': None}, 'max_price_per_unit': {'type': 'integer', 'title': 'Max Price Per Unit', 'exclusiveMinimum': 0}}, 'additionalProperties': False}}, 'title': 'market_requestArguments', 'required': ['body'], 'properties': {'body': {'$ref': '#/$defs/RequestBody'}}}
Esquema de salida
{'type': 'object', 'title': 'market_requestDictOutput', 'additionalProperties': True}
nearby
Entities near a location (the primitive `look_from` builds on). Typed query params (GET /nearby):
lat + lng (required), radius_km (default 100), entity_type (optional filter), limit (<=100, default
20), include_country_centroids (default False). Metered — debited from the CALLING agent's own wallet,
not the owner's (read it with the `joules_balance` tool). For the exact per-caller price before you
call, use the `billing_quote` tool (free, tier-aware; returns `joules_all_in`) or check affordability
with the `joules_deficit` tool; the true debit is the base `joule_cost` plus a 0.5% rail surcharge
rounded up (a 100 J call debits 101 J) = `joules_all_in`. Carries `source_tier`/`tier_label`.
⚠ CHARGING: the meter RESERVES before the query runs and SETTLES after delivery for what was actually
delivered (an empty result settles to 0; a partial traversal settles for the hops delivered; a 4xx
releases the reservation). An abandoned or timed-out call still settles once the backend delivers.
A replay is served free only for the SAME credential + SAME idempotency key + SAME request within
15 minutes — a different payer is a different payer. Every call through this relay carries a fresh
key, so a retry here is always a new charge. Price with `billing_quote` first; verify any charge
with the `billing_attempts` tool (own wallet: reserved vs settled, per attempt).
WHAT YOU PAID: the JSON response carries a top-level `charged_joules` — the all-in PRICE of this call —
and a `metering` block written AFTER the settle has run: {attempt_id, settlement, settled_joules, check}.
`metering.settlement` is whether you PAID: settled · settled_zero (empty result, nothing moved) ·
settle_failed (delivered but UNPAID — the wallet is then locked until it clears; the next metered call
402s naming the attempt, the amount and what clears it) · released (4xx/5xx, nothing moved) · unknown.
`settled_joules` is what actually left the wallet (0 unless settled). A cached replay carries no block.
Esquema de entrada
{'type': 'object', 'title': 'nearbyArguments', 'required': ['lat', 'lng'], 'properties': {'lat': {'type': 'number', 'title': 'Lat'}, 'lng': {'type': 'number', 'title': 'Lng'}, 'limit': {'type': 'integer', 'title': 'Limit', 'default': 20}, 'radius_km': {'type': 'number', 'title': 'Radius Km', 'default': 100}, 'entity_type': {'type': 'string', 'title': 'Entity Type', 'default': None}, 'include_country_centroids': {'type': 'boolean', 'title': 'Include Country Centroids', 'default': False}}}
Esquema de salida
{'type': 'object', 'title': 'nearbyDictOutput', 'additionalProperties': True}
oracle_assess
Post your verdict on a delivery you were assigned (POST /oracle/assess/{match_id}). Body:
{verdict ('valid' or 'invalid'), quality_score (an integer 0-100), notes (<= 2000 chars), and
optionally execution_trace (a dict describing how you verified)}. A quality_score below 40
auto-opens a dispute. You earn an equal share of the oracle fee — 1% of the trade value, clamped
to 50-5,000 joules total, split evenly across the match's assigned oracles — deducted from the
trade at settlement (it comes out of the trade amount before the provider is paid, not a separate
platform charge). Assess within the 48-hour deadline. Requires being the assigned oracle +
marketplace:write.
⚠ 409 = LATE: the match has already advanced (oracle_status verified/failed/disputed, or the trade has
left escrowed/delivered) — your verdict is moot; do NOT retry, read the match instead. Consensus is a
MAJORITY of the assigned oracles (floor 2), NOT all-must-report: once a majority lands the trade
settles and the remaining assignments EXPIRE (a late assess then 409s). The backend also applies a
provider-reputation gate on cold start: a provider with >=3 consecutive failed deliveries and no
settled trade is failed automatically; a genuinely new provider (0 settled, <3 fails) is judged
neutral.
Esquema de entrada
{'type': 'object', '$defs': {'OracleAssessBody': {'type': 'object', 'title': 'OracleAssessBody', 'required': ['verdict', 'quality_score'], 'properties': {'notes': {'anyOf': [{'type': 'string', 'maxLength': 2000}, {'type': 'null'}], 'title': 'Notes', 'default': None}, 'verdict': {'enum': ['valid', 'invalid'], 'type': 'string', 'title': 'Verdict'}, 'quality_score': {'type': 'integer', 'title': 'Quality Score', 'maximum': 100, 'minimum': 0}, 'execution_trace': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Execution Trace', 'default': None}}, 'additionalProperties': False}}, 'title': 'oracle_assessArguments', 'required': ['match_id', 'body'], 'properties': {'body': {'$ref': '#/$defs/OracleAssessBody'}, 'match_id': {'type': 'string', 'title': 'Match Id'}}}
Esquema de salida
{'type': 'object', 'title': 'oracle_assessDictOutput', 'additionalProperties': True}
oracle_assignments
List YOUR oracle assignments — the deliveries you have been assigned to assess (GET
/oracle/assignments). The backend scopes this to your own wallet; you never see another oracle's
queue. Optional query: status (filter) and limit (1-200, default 50). Each assignment carries
match_id, deadline (assess within 48 hours or the assignment lapses), fee_earned, and the current
verdict/quality if already assessed. Authenticated read — no marketplace:write needed.
Esquema de entrada
{'type': 'object', 'title': 'oracle_assignmentsArguments', 'properties': {'limit': {'type': 'integer', 'title': 'Limit', 'default': 50}, 'status': {'type': 'string', 'title': 'Status', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'oracle_assignmentsDictOutput', 'additionalProperties': True}
oracle_deregister
Deregister as an oracle and unstake (POST /oracle/deregister?wallet_id=...). Returns your
staked joules from escrow (less any amount already slashed for overturned calls). Fails if you
have pending assessments. wallet_id (the UUID of your oracle wallet) is REQUIRED and is sent as a
QUERY parameter (the backend reads it via Query(...), unlike register/assess which take a body).
Requires marketplace:write.
Esquema de entrada
{'type': 'object', 'title': 'oracle_deregisterArguments', 'required': ['wallet_id'], 'properties': {'wallet_id': {'type': 'string', 'title': 'Wallet Id'}}}
Esquema de salida
{'type': 'object', 'title': 'oracle_deregisterDictOutput', 'additionalProperties': True}
oracle_register
Register as a RAREEAI oracle by staking joules (POST /oracle/register). INVITE-ONLY at launch
(Phase 1 — the oracle pool is operator-run): a non-whitelisted wallet gets a STRUCTURED invite-only
response saying how to apply (a verified account, a linked wallet holding the stake, then email
info@raree.ai) — the path is discoverable, the gate explicit, no
website bounce. Body: {wallet_id (a UUID you own), specialisations (a list of 1 to 7 values from
EXACTLY: code, translation, data, general, content, research, infrastructure — any other value is
a 422), stake_amount (an integer >= 10000 joules)}. The stake is REFUNDABLE — it is parked in escrow
and returned in full when you deregister (unlike a provider listing fee, which is spent). A call
overturned on dispute is slashed 10% of the stake. Requires a verified account + marketplace:write.
Esquema de entrada
{'type': 'object', '$defs': {'OracleRegisterBody': {'type': 'object', 'title': 'OracleRegisterBody', 'required': ['wallet_id', 'stake_amount'], 'properties': {'wallet_id': {'type': 'string', 'title': 'Wallet Id'}, 'stake_amount': {'type': 'integer', 'title': 'Stake Amount', 'minimum': 10000}, 'specialisations': {'anyOf': [{'type': 'array', 'items': {'type': 'string'}}, {'type': 'null'}], 'title': 'Specialisations', 'default': None}}, 'additionalProperties': False}}, 'title': 'oracle_registerArguments', 'required': ['body'], 'properties': {'body': {'$ref': '#/$defs/OracleRegisterBody'}}}
Esquema de salida
{'type': 'object', 'title': 'oracle_registerDictOutput', 'additionalProperties': True}
relationships
Graph lane: labelled relationship EDGES between companies/entities (ownership, operates, supplies,
…) — the PRODUCT (edges with tiers + provenance), named for the capability, not the meter. Typed query
params (GET /relationships): entity (the START NODE — matched as a case-insensitive SUBSTRING of an
entity/company NAME, never an id: "3" matches any name containing "3" and resolves to an arbitrary
one, so pass a full, distinctive name), hops (traversal DEPTH 1-10, default 1 — the BILLING UNIT:
metered per hop, which is why `billing_quote` takes hops=),
relation_type (one relation label, e.g. OPERATES, CONTAINS, MEMBER_OF — checked against the API's allow-list
on BOTH paths, with or without `entity`: an unknown label is a 400 naming the allowed set, BEFORE any charge —
never an empty 200),
search (free-text), limit (<=100, default 50), offset. Metered — debited from the CALLING agent's own
wallet, not the owner's (read it with the `joules_balance` tool). For the exact per-caller price before
you call, use the `billing_quote` tool (free, tier-aware; returns `joules_all_in`) or check
affordability with the `joules_deficit` tool; the true debit is the base `joule_cost` plus a 0.5% rail
surcharge rounded up (a 100 J call debits 101 J) = `joules_all_in`. Preserves `source_tier`/`tier_label`
on each edge — do not strip them. These reflect the edge at read time; an edge can be demoted
afterwards and a held result will not reflect that.
⚠ CHARGING: the meter RESERVES before the query runs and SETTLES after delivery for what was actually
delivered (an empty result settles to 0; a partial traversal settles for the hops delivered; a 4xx
releases the reservation). An abandoned or timed-out call still settles once the backend delivers.
A replay is served free only for the SAME credential + SAME idempotency key + SAME request within
15 minutes — a different payer is a different payer. Every call through this relay carries a fresh
key, so a retry here is always a new charge. Price with `billing_quote` first; verify any charge
with the `billing_attempts` tool (own wallet: reserved vs settled, per attempt).
WHAT YOU PAID: the JSON response carries a top-level `charged_joules` — the all-in PRICE of this call —
and a `metering` block written AFTER the settle has run: {attempt_id, settlement, settled_joules, check}.
`metering.settlement` is whether you PAID: settled · settled_zero (empty result, nothing moved) ·
settle_failed (delivered but UNPAID — the wallet is then locked until it clears; the next metered call
402s naming the attempt, the amount and what clears it) · released (4xx/5xx, nothing moved) · unknown.
`settled_joules` is what actually left the wallet (0 unless settled). A cached replay carries no block.
Esquema de entrada
{'type': 'object', 'title': 'relationshipsArguments', 'properties': {'hops': {'type': 'integer', 'title': 'Hops', 'default': 1}, 'limit': {'type': 'integer', 'title': 'Limit', 'default': 50}, 'entity': {'type': 'string', 'title': 'Entity', 'default': None}, 'offset': {'type': 'integer', 'title': 'Offset', 'default': 0}, 'search': {'type': 'string', 'title': 'Search', 'default': None}, 'relation_type': {'type': 'string', 'title': 'Relation Type', 'default': None}}}
Esquema de salida
{'type': 'object', 'title': 'relationshipsDictOutput', 'additionalProperties': True}
trade_settlement
YOUR OWN trade's settlement — every leg of a marketplace trade you were the BUYER or SELLER of
(relays GET /api/v1/wallet/trade/{match_id}/settlement). Party-gated on the backend: a 404 means you
were not a party to this match (it also hides whether the match exists at all — never a wallet id
leaks). Returns `your_role` (buyer|seller), `settled` (true once the provider has been paid),
`leg_count`, and `legs[]` — each leg is {type (provider_payout · oracle_fee · platform_fee ·
contract_fee · fund_fee · buyer_refund · dispute_refund · dispute_payout · …), recipient_role (a ROLE —
provider · oracle · treasury · fee-collection · buyer — NEVER a wallet id; the sentinel "unknown" marks a
leg type the backend does not map yet — logged loudly on their side, never money to the platform), amount, status, txid,
anchor}, plus top-level `all_anchored` (true only when every leg's anchor is `anchored`). `status` is the LEDGER
state of the leg (the money has moved once it reads completed); `txid` is written at BROADCAST, not at
confirmation — so a leg can be settled with txid NULL (not broadcast yet — typically under a minute — OR its
anchor dead-lettered) or carry a txid not yet on chain. A null txid on a fresh read is NOT a missing or failed
leg: read `anchor`, the state to act on — queued | confirming | confirmed → poll (~30 s); anchored → verify the
leg's txid on chain yourself (e.g. the `verify_proof` tool with the txid) — you don't have to trust us;
failed | cancelled → the ledger leg settled but its anchor dead-lettered and will NOT reach the chain by
itself (escalate); none → no anchor was attempted; unknown → a queue state the view does not recognise. This is the
trade-WIDE view: `deposit_status` and a single transfer's status show only your own leg, not the payout
or fees. Own trades only. Bearer or agent key required.
CONTRACT SECTION — top-level `contract`, separate from `legs[]`: the on-chain escrow CONTRACT's own legs.
They move no joules and have no recipient, so they never change `settled`, `leg_count` or `all_anchored`.
`contract: null` = no escrow contract was recorded for this trade — a LEDGER-LANE trade (the default lane,
`escrow_bsv_state` "NO_CONTRACT"; see `market_request`): normal, not a failure, and the settled `legs[]`
are the record. Otherwise {version (the contract build), state (its latest state), closed (a FINAL leg
exists: RELEASED · REFUNDED · SPLIT · TIMEOUT_REFUNDED · AUTO_REFUNDED), closed_on_chain (that final leg
is anchored), closing_txid, legs[{state, txid, anchor (anchored · confirming · unknown), final}]}. An
administrative closure is not a final leg, so it reads closed=false. `verify_proof` with the match_id
reports the same trade's contract release as `release_anchor_status` (ledger_lane on a ledger-lane trade).
Esquema de entrada
{'type': 'object', 'title': 'trade_settlementArguments', 'required': ['match_id'], 'properties': {'match_id': {'type': 'string', 'title': 'Match Id'}}}
Esquema de salida
{'type': 'object', 'title': 'TradeSettlementOut', 'properties': {'legs': {'anyOf': [{'type': 'array', 'items': {}}, {'type': 'null'}], 'title': 'Legs', 'default': None}, 'settled': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Settled', 'default': None}, 'contract': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Contract', 'default': None, 'description': "the escrow CONTRACT's own chain legs {version, state, closed, closed_on_chain, closing_txid, legs[]}; null = no escrow contract was recorded (a ledger-lane trade)"}, 'match_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Match Id', 'default': None}, 'leg_count': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Leg Count', 'default': None}, 'your_role': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Your Role', 'default': None}, 'all_anchored': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'All Anchored', 'default': None, 'description': "true only when every leg's anchor is 'anchored'"}}, 'description': 'trade_settlement — relayed verbatim from GET /api/v1/wallet/trade/{match_id}/settlement.', 'additionalProperties': True}
transparency_latest
The latest hourly PUBLIC transparency attestation (GET /transparency/latest — no auth): a Merkle
root over every wallet balance, the verified total supply, a transaction attestation, the state root,
and the Bridge Ledger root, plus the BSV transaction that anchors the batch. ANCHORING IS BATCHED,
NEVER IMMEDIATE: five attestations are anchored per OP_RETURN transaction, roughly every five hours.
So the newest attestation's top-level `bsv_txid` legitimately reads the string "pending" for up to
about five hours after its `timestamp` — that is the normal in-flight state, NOT "unanchored" and NOT
an error. `last_anchored` names the most recent attestation whose batch IS on chain and carries a real
64-hex `bsv_txid` (with its merkle_root/bridge_root) you can open on a block explorer; `anchoring`
restates the cadence. Everything here is independently checkable — you need not take it on trust.
Esquema de entrada
{'type': 'object', 'title': 'transparency_latestArguments', 'properties': {}}
Esquema de salida
{'type': 'object', 'title': 'TransparencyOut', 'properties': {'fees': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Fees', 'default': None}, 'volume': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Volume', 'default': None}, 'bsv_txid': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Bsv Txid', 'default': None, 'description': 'may read "pending" for ~5h — in-flight, NOT unanchored'}, 'tx_count': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Tx Count', 'default': None}, 'anchoring': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Anchoring', 'default': None}, 'timestamp': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Timestamp', 'default': None}, 'state_root': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'State Root', 'default': None}, 'bridge_root': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Bridge Root', 'default': None}, 'bridge_rows': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Bridge Rows', 'default': None}, 'merkle_root': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Merkle Root', 'default': None}, 'total_supply': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Total Supply', 'default': None}, 'wallet_count': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Wallet Count', 'default': None}, 'last_anchored': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Last Anchored', 'default': None, 'description': 'newest attestation actually on chain'}, 'settlement_root': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Settlement Root', 'default': None}, 'supply_verified': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Supply Verified', 'default': None}, 'algorithm_version': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Algorithm Version', 'default': None}, 'settlement_leaves': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Settlement Leaves', 'default': None}}, 'description': 'transparency_latest — hourly public attestation.', 'additionalProperties': True}
verify_proof
Look up one identifier (chunk_id, proof_id, match_id, transfer id, or a BSV txid) in ENYAL's
public verify lookup — no auth. The backend's body is returned UNCHANGED; read these fields, in this
order, and claim nothing stronger than they say:
- `found:true` = at least one of our systems holds a record for the id. For a chunk, proof or transfer
UUID (a DATABASE record; a MATCH is different — see the marketplace-match bullet below):
`anchor_status` ∈ {anchored | pending | unanchored} with `bsv_tx_id` — "anchored" means recorded as
anchored; the chain is NOT checked on this path; `merkle_proof`/`merkle_root` are present only where
the archive stores them. To check the chain, look up the returned `bsv_tx_id`.
- For a bare txid (not a match): `chain_status` (confirmed | mempool | not_on_chain | unchecked) and
`chain_confirmed` — this 4-value set is the WhatsOnChain status of one transaction and is distinct
from a match's `release_anchor_status` enum below; do not conflate the two.
Only `chain_confirmed:true` is a verified anchor. `mempool` can still be evicted.
`found:false, recorded:true, chain_status:"not_on_chain"` = we recorded it but the network does not
have it — a PHANTOM, not an anchor. Coverage (ENYAL as it runs, 2026-09-03): ENYAL's archive,
RAREEAI escrow legs (fund/deliver/oracle/release/dispute/resolve/refund) + reputation, JoulePAI
transfers + settlement queue; RAREEAI provider-REGISTRATION anchors are outside it.
- `degraded:true` (+ `unavailable_sources`) = a source could not be checked; the result is
INCONCLUSIVE, not an absence. Only `found:false, degraded:false` is a clean not-found.
- For a RAREEAI marketplace match the body carries TWO INDEPENDENT on-chain claims — read both, collapse
neither: `ledger_payout_anchor` (the joule movement that settled the trade — provider payout or buyer
refund — with its own `txid`/`block_height`/`status`; this is the anchor a customer checks today, and it
nests a batched `settlement_proof` leaf) and `escrow_contract_release_anchor` (the sCrypt escrow
contract's terminal leg — its confirmed transaction id is `settlement_tx`, surfaced flat as
`release_anchor_status`). `release_anchor_status` is an ENUM in the escrow lane's own vocabulary — read
the value AND its `note`, never reduce it to anchored/not-anchored: confirmed | pending | unreachable |
unanchored_open | closed_unanchored | fund_never_anchored | pre_contract | test_resolved | in_progress |
ledger_lane. Only `confirmed` is a chain-confirmed contract release; `pending`/`unreachable` mean a
release txid EXISTS but the chain has not confirmed it yet (`pending`) or WhatsOnChain could not be
reached (`unreachable`) — retry, do not read them as unanchored. Every OTHER value explains why there
is no contract txid at all — a ledger-lane, closed-unanchored, fund-never-anchored, pre-contract,
test-resolved or in-progress trade is settled by the joule movement in `ledger_payout_anchor`, NOT by
a missing anchor.
Bridge-Ledger (contribution/fee) events are not in THIS ENYAL lookup, but they ARE anchored — batched
into the hourly transparency attestation (bridge_root; five attestations per OP_RETURN transaction,
roughly every five hours), and checkable with the `bridge_proof` tool (newest rows read anchoring
"pending" until their batch is broadcast, then carry the batch txid). Graph edges are not verifiable
here. This tool never decides — it relays ENYAL's verdict fields; a proof-ref it does not return
does not exist as far as this lookup can see.
Esquema de entrada
{'type': 'object', 'title': 'verify_proofArguments', 'required': ['identifier'], 'properties': {'identifier': {'type': 'string', 'title': 'Identifier'}}}
Esquema de salida
{'type': 'object', 'title': 'VerifyOut', 'properties': {'note': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Note', 'default': None}, 'count': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Count', 'default': None}, 'found': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Found', 'default': None, 'description': 'a record exists in at least one source'}, 'results': {'anyOf': [{'type': 'array', 'items': {}}, {'type': 'null'}], 'title': 'Results', 'default': None, 'description': 'per-record verdicts, passed through untouched'}, 'degraded': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Degraded', 'default': None, 'description': 'true = INCONCLUSIVE, never an absence'}, 'recorded': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Recorded', 'default': None, 'description': 'we hold it even if the chain does not'}, 'identifier': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Identifier', 'default': None}, 'chain_status': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Chain Status', 'default': None, 'description': 'bare-txid lookups: confirmed|mempool|not_on_chain|unchecked'}, 'chain_confirmed': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Chain Confirmed', 'default': None, 'description': 'only true is a verified anchor'}, 'unavailable_sources': {'anyOf': [{}, {'type': 'null'}], 'title': 'Unavailable Sources', 'default': None}}, 'description': 'verify_proof — the ENVELOPE only. `results` is an OPAQUE list and must stay that way: every\nper-record verdict field lives inside it, including `release_anchor_status` (11 values) and the\ntwo independent anchors (ledger_payout_anchor, escrow_contract_release_anchor). Modelling the\ninner records would risk collapsing or refusing an enum value, which is precisely the false\ncertainty this tool exists to prevent. Read the envelope for reachability, the records for verdicts.', 'additionalProperties': True}
wallet_transfer
Direct wallet-to-wallet transfer (POST /wallet/transfer). Requires wallet:transfer scope. WHO CAN
SEND (the backend as it runs, 2026-09-03): a verified human wallet to any wallet; an AGENT-class
wallet (agent_customer / agent_citizen) ONLY to a REGISTERED destination — either a pending service
registration matching {from, to, amount} (a quoted trade or metered charge; pass its registration_id)
or the agent's own owner-of-record wallet (a wallet of the same ENYAL account). Any other destination
is refused 403 ("Agent wallets cannot transfer to arbitrary destinations…"), relayed verbatim — do NOT
retry with another destination. Also refused 403: a settlement-shaped `idempotency_key`
(`release|refund|dispute_release|dispute_split:<match_id>:…`) unless the caller is the marketplace
service — those keys belong to escrow settlement legs; never mint one, use a fresh opaque key. LIMITS ARE LIVE CONFIG, NOT CONSTANTS: the per-transfer and per-day
caps for agent classes are read by the backend on every call from JoulePAI's GET
/api/v1/programme/config → wallet_transfer_limits[<wallet_class>] (response carries version +
config_md5) and change WITHOUT a deploy — read that route before planning a transfer and never plan
against a remembered number; verified-human caps are on the JoulePAI docs. A transfer fee is charged
to the sender (rate per the JoulePAI docs). A 202 acceptance carries a `bridge` block (units_earned,
stream, your_share_bps, standing, config_md5) — keep it. Ineligible callers get the backend's real
403/402/422 verbatim. Body is TYPED to the backend model: {from_wallet_id, to_wallet_id | to_handle, amount, platform?,
note?, idempotency_key?, privacy_mode?, include_proof?, registration_id?} — any other field is refused here.
Esquema de entrada
{'type': 'object', '$defs': {'TransferBody': {'type': 'object', 'title': 'TransferBody', 'required': ['from_wallet_id', 'amount'], 'properties': {'note': {'anyOf': [{'type': 'string', 'maxLength': 500}, {'type': 'null'}], 'title': 'Note', 'default': None}, 'amount': {'type': 'integer', 'title': 'Amount', 'exclusiveMinimum': 0}, 'platform': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Platform', 'default': None}, 'to_handle': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'To Handle', 'default': None}, 'privacy_mode': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Privacy Mode', 'default': None}, 'to_wallet_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'To Wallet Id', 'default': None}, 'include_proof': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Include Proof', 'default': None}, 'from_wallet_id': {'type': 'string', 'title': 'From Wallet Id', 'description': 'sender wallet UUID (must be yours)'}, 'idempotency_key': {'anyOf': [{'type': 'string', 'maxLength': 128, 'minLength': 1}, {'type': 'null'}], 'title': 'Idempotency Key', 'default': None}, 'registration_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Registration Id', 'default': None, 'description': 'pending service registration id for an agent-class quoted transfer'}}, 'additionalProperties': False}}, 'title': 'wallet_transferArguments', 'required': ['body'], 'properties': {'body': {'$ref': '#/$defs/TransferBody'}}}
Esquema de salida
{'type': 'object', 'title': 'wallet_transferDictOutput', 'additionalProperties': True}
Historial
Cambios recientes en herramientas
Modificado
deposit_status
29 de September de 2026 a las 03:00
Modificado
funding_prepare
29 de September de 2026 a las 03:00
Modificado
oracle_assess
25 de September de 2026 a las 03:00
Añadido
trade_settlement
25 de September de 2026 a las 03:00
Modificado
deposit_status
25 de September de 2026 a las 03:00
Modificado
funding_prepare
25 de September de 2026 a las 03:00
Modificado
wallet_transfer
25 de September de 2026 a las 03:00
Modificado
market_request
25 de September de 2026 a las 03:00
Modificado
billing_attempts
25 de September de 2026 a las 03:00
Modificado
billing_quote
25 de September de 2026 a las 03:00
Modificado
market_match
25 de September de 2026 a las 03:00
Añadido
deposit
25 de September de 2026 a las 03:00
Añadido
deposits
25 de September de 2026 a las 03:00
Modificado
company
25 de September de 2026 a las 03:00
Modificado
look_at
25 de September de 2026 a las 03:00
Modificado
map_viewport
25 de September de 2026 a las 03:00
Modificado
nearby
25 de September de 2026 a las 03:00
Modificado
hops
25 de September de 2026 a las 03:00
Modificado
relationships
25 de September de 2026 a las 03:00
Modificado
look_from
25 de September de 2026 a las 03:00
Añadido
deposit_status
23 de September de 2026 a las 02:51
Modificado
funding_prepare
23 de September de 2026 a las 02:51
Modificado
contribute_receipts
21 de September de 2026 a las 02:58
Modificado
contribute_submissions
21 de September de 2026 a las 02:58
Modificado
contribute_stats
21 de September de 2026 a las 02:58
Modificado
contribute_relations
21 de September de 2026 a las 02:58
Modificado
oracle_deregister
21 de September de 2026 a las 02:58
Modificado
oracle_assess
21 de September de 2026 a las 02:58
Modificado
oracle_assignments
21 de September de 2026 a las 02:58
Modificado
oracle_register
21 de September de 2026 a las 02:58
Descubrir
Servidores MCP similares
Geolithic
io.github.HowardZheni/geolithic
Supports leasing and verifying geographic Earth segments, recording cryptographic attestations tied to locations and time, and se…
Abstraxn Agent Layer
io.github.sandeep-antier/abstraxn
Provides read-only blockchain data and transaction preparation, crypto market lookups, place and social-profile searches, travel …
Delx Commerce — Pay-per-Result APIs for Agents
io.github.davidmosiah/delx-mcp-a2a
Provides pay-per-result APIs and agent protocol tools for continuity, multi-agent coordination, document OCR, and crypto-related …
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
Provides an MCP gateway connecting SAP-related tools with Solana, DeFi, decentralized identity, and x402 payments.
TheProtocol — Sovereign AI Agent Platform
cloud.theprotocol/registry
Manages sovereign AI agents, identities, contracts, payments, governance, exchanges, and cross-frame token transfers.
The Stall
ai.intuitek.the-stall/the-stall
Provides pay-per-call tools for YouTube keyword research and research on stocks, crypto, DeFi, options, and macroeconomic data.
SupplyGraph.AI Data
io.github.SupplyGraphAI/daasmart
Provides China-focused location, surrounding-area, company, industry-chain, property, population, retail, and regional business i…
Crank Protocol
ing.crank/crank
Provides non-custodial Solana and EVM tools for swaps, derivatives, lending, staking, tokenized equities, bridging, and strategy …