Build with Phasoric
Phasoric is a user-owned decision-intelligence platform. Developer surfaces let external products, scripts, agents, and approved partner applications continue work in Phasoric without turning those integrations into the authority for a user's knowledge, decisions, or actions.
Choose an integration
| You want to… | Start with | Availability |
|---|---|---|
| Let a user continue external work in Phasoric | Handoff API | Public integration contract; user can accept into a Free account |
| Let an AI client work with a Phasoric Hosted vault | MCP | Entitled with plan-specific quotas: Premium, Professional, Developer & Agent, or Team |
| Read or mutate a Phasoric Hosted vault from code | Developer REST API | Entitled: Developer & Agent or Team |
| Connect Zapier, n8n, webhooks, or event pipelines | Automation & OpenAPI | Entitled and workspace-governed |
| Build another application powered by Phasoric | Product Runtime | First-party / approved partner path |
| Define reusable domain intelligence | Vertical Intelligence Packs | First-party / approved partner preview |
| Define a different Phasoric product experience | Product Experience Packs | First-party / approved partner preview |
The boundary that matters
Phasoric is local-first. A hosted developer surface does not automatically gain access to browser-local knowledge.
Local-only Phasoric vault
↓
user explicitly connects/maps a logical vault to Phasoric Hosted
↓
Hosted mapping / explicit product grant
↓
REST, MCP, Product Runtime or automation
If a logical vault is local-only, hosted APIs report that the capability is unavailable rather than silently uploading the vault to create API symmetry.
Core governance invariants
Developer integrations do not replace Phasoric's internal authority model:
- Pulse detects meaningful change.
- Strata owns confirmed decisions.
- Forge remains the boundary for consequential actions and governed mutations.
- External content is treated as data, not as system instruction.
- Shared agent context is bounded by current Context Scope and audience authority.
- Provenance remains separate from acquisition/marketing attribution.
Public docs versus paid usage
The Developer Center is public. Some APIs require a paid plan because they operate against authenticated hosted data.
Reading these docs never grants an entitlement. A hostname or Product Experience never grants access to a workspace or vault.
Start here
- New to the platform: Getting started.
- Adding a “Continue in Phasoric” button: Handoff API.
- Connecting an agent: MCP.
- Writing a backend integration: Developer REST API.
- Building a separate product: Product Runtime.