PacSpace MCP
PacSpace MCP is in development. This is a high-level preview of where it fits for agents.
Coming soon
PacSpace MCP is in development. This page is a high-level preview. It does not describe a released integration. The shape of the final interface, the tools it exposes, and its availability are all subject to change.
PacSpace MCP is an upcoming interface to PacSpace for agentic systems, built on the Model Context Protocol. The goal is to let a compatible agent work with verified deltas, receipts, and proofs without writing a custom REST client for every operation.
Use When
This page is for orientation only. It is useful when an agent's operator is evaluating future integration paths or trying to decide how much custom REST plumbing to build today.
It is not a reference for a shipping product. For anything an agent needs to do right now, start with Capabilities and the TypeScript SDK.
Inputs
- Interest in building or evaluating an MCP-compatible agent.
- A willingness to revisit this page as PacSpace MCP moves from preview to release.
What This Preview Commits To
A small number of things are stable enough to say today:
- PacSpace MCP will be grounded in the same public primitives documented across this site — the verified delta, the receipt, the proof root, the checkpoint.
- It will respect the same environment model as the Balance API: dedicated Sandbox and Production infrastructure, selected through the same
pk_test_*/pk_live_*credential convention. - It will preserve the public data boundary described in Overview: deltas stay private, proofs are safe to share.
Everything else is intentionally open while the design is finalized.
What This Preview Does Not Commit To
This page intentionally does not describe specific tools, resources, authentication flows, transport details, release dates, or delivery timing. Those details will be published when the interface is released and not before.
An agent should not attempt to reverse-engineer a stub interface from this page. There is nothing to implement against yet.
What an Agent Can Do Today
While PacSpace MCP is in development, agents can integrate against PacSpace through the channels that are already production-ready:
| Need | Use |
|---|---|
| Emit, derive, compare, checkpoint | TypeScript SDK or the Balance API directly |
| React to verification events | Webhooks and the Autonomous Agent Pattern |
| Hand a counterparty something verifiable | Proofs for Agents |
| Design a metering loop | Integration Patterns |
Agents that build on these surfaces today will find their integrations continue to work when PacSpace MCP ships. MCP is an additional interface, not a replacement for the public API.
Staying Updated
This page will be rewritten when PacSpace MCP enters public preview. Until then, treat every detail not listed under "What This Preview Commits To" as undecided.
Failure Modes
- Treating this page as a reference and building against assumptions it does not make.
- Delaying work on a production agent in expectation of a specific MCP release date.
- Assuming MCP will replace the existing API surface — it is designed to complement it, not replace it.
Related Pages
- Overview — start here for a new agent integration.
- Capabilities — the operations available to an agent today.
- Authentication — how agents authenticate to PacSpace.
- TypeScript SDK — the SDK surface agents integrate against today.