---
name: ardaro-agent-utilities
description: Evaluate deterministic context formatting, intent classification, submitted budget checks and billing reconciliation through Ardaro's x402 MCP gateway.
---

# Ardaro advisory agent utilities

Connect a Streamable HTTP MCP client to `https://agents.getardaro.com/mcp`.
The four utilities process supplied inputs in memory without a model call.
Results require human review. They do not enforce a budget, execute a route,
verify service delivery, or post financial records.

## Free evaluation

For each tool below, call `get_<tool>_service_status` and `get_<tool>_example`
with `{}`. These free tools return cached readiness/terms or a fixed synthetic
example. They accept no arbitrary input and authorize no payment.

| Paid tool | USDC per accepted call | REST path segment |
| --- | --- | --- |
| `compress_agent_context` | 0.05 | `context-compression` |
| `route_model_intent` | 0.15 | `intent-routing` |
| `authorize_agent_spend` | 0.10 | `budget-check` |
| `reconcile_api_ledger` | 0.25 | `ledger-reconciliation` |

For a path segment above, the canonical paid resource is
`https://agents.getardaro.com/v1/agent-utilities/<segment>/analyze`.
Replace `analyze` with `status`, `example` or `openapi.json` for free reads.
Use the published request schema and example; reject unknown fields locally.

## Interpret results accurately

- `compress_agent_context`: input `raw_conversation_history`, 1–32768 characters.
  Reduces runs of three or more line breaks to two. Preserves words and role
  headers. The candidate needs review: whitespace can matter in code or data.
  It reports no verified token savings or semantic equivalence.
- `route_model_intent`: input `intent_payload`, 1–32768 characters. A keyword
  heuristic labels structured-calculation review or general-text review.
  It chooses no actual model and proves no quality, price or speed advantage.
- `authorize_agent_spend`: compare a proposed cost with supplied policy and
  history using exact micro-unit arithmetic. Policy and history are unauthenticated.
  A within-limits result grants no authority, creates no reservation and cannot
  block calls made elsewhere. The comparison excludes this tool's 0.10 USDC fee.
  An unfavorable advisory result is still a completed billable analysis.
- `reconcile_api_ledger`: compare up to 100 supplied billing and usage records
  per list by request ID, amount and currency. Duplicate IDs are rejected.
  Missing or mismatched observations are flagged; matching observations do not
  prove delivery or genuine telemetry. USD and USDC remain separate currencies.

## Runnable integrations and dated acceptance evidence

The [public examples repository](https://github.com/ashevilleislove/ardaro-agent-examples)
contains framework adapters, pinned dependency versions and execution reports.
Start with the [utility integration guide](https://github.com/ashevilleislove/ardaro-agent-examples/blob/main/docs/agent-utilities.md).

All four utility REST endpoints passed one synthetic owner acceptance check each,
verified September 13, 2026 UTC: exact response schema, expected result and Base
USDC settlement. [Inspect the scoped proof and transaction links](https://github.com/ashevilleislove/ardaro-agent-examples/blob/main/evidence/owner-rest-tests-20260913.json).
The status field `settlement_proven` refers only to this dated REST evidence when
the deployment identity, service version and price match. Read its
`settlement_proven_transport` and `acceptance_evidence` fields. It is separate
from current `ready` availability and does not establish utility paid MCP
execution, customer adoption or a performance benchmark.

## Explicit paid authorization

Ordinary MCP clients can discover and evaluate. Paid calls require an existing
x402-capable signer and an explicit caller spending policy or approval. Never
create or fund a wallet just to connect. Verify the merchant independently.
Require x402 v2 exact scheme, Base `eip155:8453`, native USDC
`0x833589fcd6edb6e08f4c7c32d4f71b54bda02913`, the exact REST resource above,
and exactly 50000 / 150000 / 100000 / 250000 atomic units for the respective tool.
The payment identifier extension is required. Payment goes in MCP
`params._meta["x402/payment"]`; settlement appears in
`result._meta["x402/payment-response"]`. A free example or 402 challenge does
not establish successful live settlement or authorize a charge.

Validate the response contract `ardaro.agent-utilities.response.v1`, service ID,
human-review policy, deterministic result identity and payment receipt. Result
hashes bind a response for comparison; they do not certify input truth.

After an uncertain payment, retry only the identical request, signed payment
and payment identifier. Do not create another authorization or change identifiers.
Stop and contact support@getardaro.com if the outcome remains unknown.

## Data boundaries

Raw utility inputs are not persisted or logged by this application. Utility
results are not cached in process. Requests and responses exist in memory during
processing; clients, network infrastructure and the operating system have their
own retention boundaries. Content-free payment and sale metadata is retained
for accounting and replay protection. Read the status document for current limits.
Submit only necessary data; omit credentials, keys and unrelated personal data.
No Ardaro customer-tenant data is accessed. These utilities do not claim A2A compliance.