# Synorb developer integration map

Choose one of the supported server-side interfaces:

- [REST API](https://synorb.com/docs/api) for deterministic requests,
  scheduled jobs, dashboards, and backend-owned product paths.
- [MCP](https://synorb.com/docs/mcp) for an interactive agent loop over
  Streamable HTTP.
- [Agent guide](https://synorb.com/agent-guide.md) for routing, scope,
  citations, quota, and failure-handling recipes.
- [OpenAPI](https://synorb.com/openapi.json) for machine-readable REST
  paths, schemas, security requirements, and quota headers.
- [Documentation MCP](https://mcp.synorb.com/docs-mcp) for public, read-only
  documentation lookup without account or content access.

## Named developer resources

- **Synorb API Documentation:** https://synorb.com/docs/api
- **Synorb OpenAPI Specification:** https://synorb.com/openapi.json
- **Synorb MCP Server Documentation:** https://synorb.com/docs/mcp
- **Synorb Authentication Documentation:** https://synorb.com/auth.md
- **Synorb SDK Documentation:** https://synorb.com/sdk
- **Synorb CLI Documentation:** https://synorb.com/docs/cli
- **Synorb sandbox/test environment:** https://synorb.com/sandbox
- **Machine-readable developer resource index:** https://synorb.com/developer-resources.json
## Authentication

REST and Core MCP use the same server-side bearer Synorb Key. Create a free
72-hour Agent Demo key with `POST https://api.synorb.com/api/connect/demo-key`, or read the
[authentication guide](https://synorb.com/auth.md). Agents that need short-lived,
scoped, revocable credentials can use the OAuth 2.0 authorization-code + PKCE
flow in that same guide; its access tokens use the identical Bearer header.
Issuer: https://api.synorb.com — authorization-server metadata at
https://api.synorb.com/.well-known/oauth-authorization-server (RFC 8414).
Each protected resource names that issuer at
/.well-known/oauth-protected-resource (synorb.com, api.synorb.com,
mcp.synorb.com). Do not put keys in URLs,
browser code, logs, prompts, or source control.

## Agent-facing REST discovery

`GET`/`POST /ask` provides authenticated natural-language stream discovery.
`POST /batch` provides a bounded, read-only batch envelope for `/ask` and
stream-search operations. See the [REST API reference](https://synorb.com/api/llms.txt)
for the exact limits and receipt contract.

## Billing and plans

See the [payments reference](https://synorb.com/payments/llms.txt) and
[public pricing](https://synorb.com/pricing.md). Payment requires explicit
account-owner confirmation at the hosted Stripe checkout; a verified webhook,
not the checkout URL, activates the entitlement.