SPYN3 developer platform / Private beta

One context layer.Two interfaces.

Connect business sources once. Then let Claude, ChatGPT, custom agents and ordinary applications reach the same permission-scoped knowledge through a hosted MCP server or REST API—with source references preserved in every retrieval path.

Download the agent skill Start with MCP

agent query

$ curl $SPYN3_API_URL/agent/query \
  -H "Authorization: Bearer $SPYN3_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "Which contracts renew this quarter?",
    "limit": 5
  }'

answer:
Three contracts contain renewal terms this quarter.

sources[3]{document_id,title,connector,score,snippet}
…

1 workspaceThe isolation and authorization boundary behind every agent call.

4 core toolsSearch, answer, inspect sources and retrieve detail without tool-catalog sprawl.

2 interfacesMCP for agent hosts; REST for applications, automations and custom runtimes.

Citations onStable document identifiers and source metadata remain part of retrieval.

Choose your path / 01

Bring the client. Keep the context.

Each guide answers a different implementation job. The underlying workspace, data sources, permissions and retrieval layer stay the same.

Portable agent skillZIP / Markdown

Give any agent the SPYN3 method

Install one client-neutral skill for evidence-first search, progressive retrieval and stable source citations over MCP or REST.

Download the skill →MCP quickstartPOST /agent/mcp

Connect an MCP-capable agent

Use the hosted Streamable HTTP endpoint and a workspace-scoped credential to expose a deliberately small tool surface.

Open MCP guide →REST quickstart/agent/*

Query from any application

Search raw passages, ask a synthesized question, list sources or inspect the available agent tools.

Open REST guide →Security modelBearer

Scope every agent explicitly

Create revocable API keys with only the permissions a workload needs, and understand the MCP OAuth path.

Review authentication →Response designTOON / JSON

Return less. Preserve proof.

Shape context for an agent's token budget while keeping the source identifiers needed to verify the answer.

Explore cited responses →

System shape / 02

Ingest once. Change clients freely.

MCP and REST are delivery surfaces, not separate data silos. Improvements to ingestion, retrieval or permission policy sit behind both.

01 / SourcesDrive, files, sites, Postgres

Business inputs enter one workspace.

02 / IngestionNormalize and index

Async, idempotent processing.

03 / RetrievalHybrid search

Semantic and exact-term discovery.

04 / BoundaryScope and cite

Workspace policy remains central.

05 / ClientsMCP or REST

Agents and apps choose their interface.

Interface status

The developer platform is available through the private beta. The dashboard provides the hosted API origin, a one-time API key secret and copy-ready MCP configuration. Public examples use environment variables because credentials and deployment origins must never be copied from documentation.

Make the second agent cheaper than the first.

Bring one real source and one real retrieval job. SPYN3 handles the shared data layer; you keep control of the client, prompt and application logic.

Request private beta access