Discovery
Machine-readable by design
Catalog, OpenAPI, x402 metadata, llms.txt, skill.md, native MCP, commercial status, and distribution status expose the live commercial surface without requiring a human landing-page flow.
Production · MCP Registry 0.5.1
SALT19 Agent Utility Grid
Utilities AI agents can discover, buy, and verify.
Production machine-to-machine infrastructure for autonomous software. Compatible agents can discover technical services through native MCP and machine-readable endpoints, receive a real x402 payment challenge, settle in Base USDC, execute the canonical tool, and receive structured results with auditable telemetry.
agent-grid / production
$mcp registry discover
✓io.github.GabrielAllit1/
salt19-agent-utility-grid@0.5.1
→POST https://api.salt19.com/mcp
✓tools/list
→tools/call dependency-go-no-go
402payment required · x402 exact
→Base USDC settlement proof
✓canonical /v1/* execution
✓D1 telemetry + reconciliation
✓structured result / receipt
0.5.1Official MCP Registry version
14Active now
20Implemented products
6Demand-gated candidates
x402 v2Base mainnet · eip155:8453
Agent-native execution
Discovery and payment are separate layers. The Grid connects them.
MCP answers “what capability can this agent use?” x402 answers “how does the agent obtain paid access?” Agent Utility Grid routes MCP through the same canonical REST execution, x402 middleware, settlement, telemetry, and reconciliation authority.
01AI / MCP client
02Official Registry
03MCP discovery
04Paid tool call
05HTTP 402
06Base USDC
07/v1/* execution
08Receipt + telemetry
Authority
One canonical paid path
Paid MCP calls route internally to the protected REST product route. The same x402 middleware, settlement logic, telemetry, and reconciliation are used regardless of whether the agent entered through MCP or REST discovery.
Evidence
Verification receipts
Decision products persist a receipt with product, subject, verdict, confidence, policy version, and a SHA-256 digest of the evidence. Receipts can also carry the governing operation ID and settlement transaction provenance.
Semantic purchase idempotency
One agent intent. At most one durable execution effect.
Version 0.5.1 retains the durable commercial-operation authority above transaction replay protection. Clients generate one stable operation ID for one intended purchase and preserve it across the unpaid challenge, payment, timeout recovery, and every retry of that same intent.
Identity
Intent gets a stable operation ID
Paid REST calls support Idempotency-Key. Paid MCP tools support _salt19_operation_id. Standard x402 clients may omit SALT19-specific identity and receive payment-proof-derived replay protection; explicit semantic identity remains recommended for the strongest at-most-once retry contract.
Concurrency
Execution is atomically claimed
Only one request can transition a commercial operation into the executing state. Concurrent retries cannot both enter the protected resource-execution boundary.
Recovery
Ambiguity fails closed
Completed operations replay the durable original result. Reusing an operation ID with a different request is rejected. Expired or ambiguous executions are quarantined as OUTCOME_UNKNOWN instead of being silently charged again.
semantic commerce retry contract
intentone autonomous purchase
operation_idstable across challenge + payment + timeout + retry
first executiondurable result persisted
retryoriginal result replayed; no second execution effect
different request409 idempotency_key_reused_with_different_request
ambiguous outcomeOUTCOME_UNKNOWN; automatic recharge blocked
Official MCP Registry
Published for standardized agent discovery.
Version 0.5.1 is the active release in the official MCP Registry. Compatible registry consumers can resolve the canonical server identity and remote streamable-HTTP MCP endpoint, while superseded releases remain in Registry history.
io.github.GabrielAllit1/salt19-agent-utility-grid
remote: https://api.salt19.com/mcp
remote: https://api.salt19.com/mcp
Native MCP behavior
Stateless discovery and tool calls
server/discoverLIVE
initializeLIVE
pingLIVE
tools/listLIVE
tools/callLIVE
verify-decision-receiptFREE
Product portfolio
Live paid utilities. Demand-gated candidate products.
The live production endpoints are authoritative for current catalog size, product state, and prices. The static HTML below is a no-JavaScript discovery fallback; when JavaScript is available, live price, state, opportunity score, and last commercial action are loaded from /commercial/status. The controller can promote only already-implemented products inside explicit policy bounds.
| Product | Route | Current price | State | Opportunity score | Last action |
|---|---|---|---|---|---|
| model-memory-fit | POST /v1/model-memory-fit | $0.05 | ACTIVE | — | — |
| url-http-preflight | POST /v1/url-http-preflight | $0.03 | ACTIVE | — | — |
| github-repo-preflight | POST /v1/github-repo-preflight | $0.10 | ACTIVE | — | — |
| npm-package-intel | POST /v1/npm-package-intel | $0.05 | ACTIVE | — | — |
| dependency-go-no-go | POST /v1/dependency-go-no-go | $0.25 | ACTIVE | — | — |
| agent-decision-preflight | POST /v1/agent-decision-preflight | $0.50 | ACTIVE | — | — |
| repo-adoption-go-no-go | POST /v1/repo-adoption-go-no-go | $0.35 | ACTIVE | — | — |
| dependency-upgrade-go-no-go | POST /v1/dependency-upgrade-go-no-go | $0.20 | ACTIVE | — | — |
| agent-code-change-risk-gate | POST /v1/agent-code-change-risk-gate | $1.25 | ACTIVE | — | — |
| agent-plan-verifier | POST /v1/agent-plan-verifier | $0.75 | ACTIVE | — | — |
| agent-claim-output-verifier | POST /v1/agent-claim-output-verifier | $0.50 | ACTIVE | — | — |
| commerce-decision | POST /v1/commerce-decision | $0.02 | ACTIVE | — | — |
| commerce-verify | POST /v1/commerce-verify | $0.03 | ACTIVE | — | — |
| commerce-receipt | POST /v1/commerce-receipt | $0.05 | ACTIVE | — | — |
| model-memory-plan | POST /v1/model-memory-plan | $0.15 | CANDIDATE | — | — |
| url-readiness-go-no-go | POST /v1/url-readiness-go-no-go | $0.15 | CANDIDATE | — | — |
| package-stack-go-no-go | POST /v1/package-stack-go-no-go | $0.50 | CANDIDATE | — | — |
| agent-decision-deep | POST /v1/agent-decision-deep | $1.50 | CANDIDATE | — | — |
| agent-solve | POST /v1/agent-solve | $2.50 | CANDIDATE | — | — |
| commerce-audit-pack | POST /v1/commerce-audit-pack | $0.10 | CANDIDATE | — | — |
Live offers and discovery state are authoritative. Candidate routes remain dormant and omitted from discovery until promoted by the bounded commercial policy.
Phase 1 Reliability Suite — LIVE
Five reliability products are live behind the same canonical commercial path.
Phase 1 adds three new products and extends two existing decision products without creating a second payment or settlement implementation.
Production smoke verified
Catalog discoveryPASS
MCP discoveryPASS
x402 payment gatingPASS
Commercial integrity
x402 v2 · Base mainnetLIVE
Payment verificationENABLED
Transaction evidenceACTIVE
Decision intelligence
Portable evidence with verifiable integrity.
Decision Grid products return bounded GO, WARN, or BLOCK outputs and can persist a verification receipt. The receipt records what was evaluated, under which policy, and the digest of the evidence that supported the result.
Receipt integrity
verified=true confirms that stored evidence matches its recorded SHA-256 digest. Each receipt preserves evaluated scope, policy context, confidence, and evidence for downstream audit and review.
{
"product": "dependency-go-no-go",
"subject": "example-package",
"verdict": "WARN",
"confidence": 0.86,
"policy_version": "...",
"evidence_digest": "sha256:...",
"receipt_id": "...",
"verified": true
}
Autonomous commercial loop
Market signals tune the catalog inside hard guardrails.
An hourly production controller observes discovery and transaction evidence, scores opportunities, and makes bounded SCALE, HOLD, DEMOTE, or eligible PROMOTE decisions. Distribution visibility is combined with payment challenges, paid executions, failures, and reconciled commercial evidence in the opportunity model.
01Market Observer
Agent402 signals, challenges, paid executions, failures, external revenue.
02Opportunity Scorer
Scores product and adjacent-family evidence under policy.
03Bounded Controller
SCALE · HOLD · DEMOTE · at most one eligible promotion.
04Price + Discovery
Adjusts within hard per-product min/max and cooldown rules.
05Persisted Evidence
D1 stores observations, cycles, decisions, policy, and performance.
Automated promotion cannot exceed the configured active-product cap.
At most one candidate promotion per cycle.
Price movement capped at $0.01 per eligible cycle.
Price changes require at least 5 validated sales over 7 days.
24-hour price-change cooldown.
Promotion requires qualified adjacent-family sales evidence.
No authority to trade assets, borrow, spam, or fabricate demand.
No arbitrary product generation or uncontrolled external spending.
Machine discovery
Agents get first-class machine discovery.
The production service publishes structured discovery surfaces for clients, crawlers, agent runtimes, MCP consumers, and x402-aware software.
Native MCP endpoint
POST https://api.salt19.com/mcp
The MCP endpoint is a protocol surface rather than a browser landing page. Use an MCP-compatible client or direct JSON-RPC request.
https://api.salt19.com/mcp
Commercial authority
The live catalog and commercial status endpoints are the authoritative source for current discovery state, offers, and prices.
Release proof
Guarded production release.
Version 0.5.1 is deployed with governed semantic purchase idempotency, external payability certification, normalized distribution, Proof402 interoperability, and late-settlement recovery. Production deployment and official MCP Registry verification are guarded release authorities.
main · production deployment guarded by GitHub Actions
agent-grid-production-credentialsSUCCESS
agent-grid-production-deploySUCCESS
agent-grid-mcp-registrySUCCESS
external payability certificationSUCCESS
Revenue verification
Commercial evidence is transaction-linked end to end.
The Grid admits commercial activity to its verified revenue record only after payment settlement and successful paid execution can be correlated to the same transaction and product route.
402 challengeOFFER
Payment proofAUTHORIZATION
Facilitator settlementSETTLEMENT
Utility resultEXECUTION
Transaction verificationVERIFIED
Revenue evidenceADMITTED
FAQ
Precise answers for builders and agents.
What is Agent Utility Grid?
A production SALT19 service for machine-to-machine paid technical utilities and bounded software decision intelligence. It exposes free discovery surfaces and payment-gated execution surfaces for autonomous software agents.
Is it in the official MCP Registry?
Yes. The canonical Registry identity is io.github.GabrielAllit1/salt19-agent-utility-grid, version 0.5.1, with remote MCP endpoint https://api.salt19.com/mcp.
How are paid MCP calls handled?
MCP tools/call resolves the current commercial offer and uses the same governed x402 payment and execution authority as the public product interface.
What network is used for production payments?
Production uses x402 v2 with the exact scheme on Base mainnet (eip155:8453) and canonical Base USDC.
How are product activations governed?
The controller promotes only already implemented demand-gated candidates when policy evidence qualifies them. Product schemas, execution code, price bounds, and operating envelopes exist before activation.
How does the Grid verify commercial activity?
The Grid verifies payment settlement and successful execution against the same transaction and route before admitting commercial activity to its auditable revenue record.
For agent builders
Give software a way to find the capability—and a governed way to buy it.
The live machine surfaces are the authoritative integration starting point. Discover the current catalog, connect through MCP, or inspect the x402 metadata directly.