The Vaultfire index
Vaultfire is more than one bond or one API. This index connects the main areas to a plain-English explanation, the relevant implementation, and its current limits.
V2 configuration, V3 source review, read-only services, local examples, deferred designs and production qualification are different states. An item appearing here does not activate it or establish that it is safe for funds.
Set an agent’s limits, define evidence, and understand how deposits, remedies and rewards differ.
V3 source review; V2 rules are separate
Start with Accountability and Partnership Bonds. The implementation and network determine consent, funding, claims and exit rules; not every bond has the same enforcement mechanism.
Check who is acting, what permission they have, and which claims have supporting evidence.
Versioned implementations and scoped evidence
Identity is not a universal trust score. Inspect each registry, authorization, delegation and reputation module’s status, signing domain, expiration and recovery rules before integration.
Discover API services, inspect request contracts and payment conditions, and recover an interrupted operation.
V2 configured catalog; V3 payments disabled
A payment challenge is not a completed operation. The dedicated x402 guide separates public discovery, synthetic local fulfillment, provider-dependent operations and durable receipts.
Let a compatible assistant inspect operations, release identity and service health without signing or paying.
Five read-only MCP tools
Use the copyable brief or the documented remote MCP endpoint. No MCP signing, payments, background push, automatic task execution or V3 value movement is implied.
Understand when an obligation settles, what proves completion, and how to avoid paying twice after an interruption.
Inspect exact module and local-flow evidence
Escrow and an HTTP receipt are different mechanisms. Use the task-escrow module’s typed milestones and blockers for protocol review; use the local HTTP guide for durable identifier, idempotency and retry behavior.
Get exact source, install supported tools, run a working local example, then find versioned operation contracts.
Local evaluation; not production qualification
The Quickstart lists pinned prerequisites, real commands, expected output and recovery. The SDK, OpenAPI and operation-status records explain supported preparation, authorization, polling and retry boundaries.
Inspect evidence for signatures, proofs, accounting, emergency controls and recovery instead of relying on a badge.
Evidence is scoped; external gates remain
Separate host tests, a fresh native binary, local runtime execution, genuine proofs, public-chain deployment and independent review. A genuine positive SP1 proof and operational/funded approvals are not supplied by this website.
Find every cataloged module, including standards integrations, deferred designs and retired paths.
Per-module disposition, not a list of active services
Use the full module catalog and architecture atlas for dependencies, resources, tests and blockers. “Ported,” “redesigned,” “deferred” and “retired” describe different outcomes; a catalog entry is not a deployed feature.
Not sure where to begin? Read the plain-English guide first. If you want to try something, choose the browser, agent or developer Quickstart.