PA
Protocol

Private API AI Integration

Connect Private API to BeforeQuery for grounded AI answers and agent actions across Protocol.

What is it?

About Private API

Private API is one of the Protocol platforms BeforeQuery connects to. Once linked, the platform's data becomes a first-class source for grounded AI answers and a target for policy-gated agent actions — the same identity, approval, and audit-log guarantees every other integration ships with.

Setup

How to connect Private API

  1. Step 01

    In the BeforeQuery dashboard, go to Integrations → Protocol and select Private API.

  2. Step 02

    Sign in to Private API with an account that has permissions to grant BeforeQuery the Protocol scopes required.

  3. Step 03

    Confirm the connection. Private API is now available as a source and action target for every playbook in your workspace.

How BeforeQuery uses Private API

What the agent does with your Private API connection

  • 01

    Extend BeforeQuery to any system that speaks Private API, without a hand-written connector.

  • 02

    Bidirectional: read from and write to Private API-compliant services from any playbook.

  • 03

    Bring your own AI clients — expose BeforeQuery via Private API so external tools can query the Context Graph.

  • 04

    Long-tail coverage: reach the systems no vendor built a connector for yet.

Use cases

What teams actually do with the Private API integration

Bring your own client

Any Private API-compatible AI IDE or chat tool can query BeforeQuery for grounded answers. Cursor, Windsurf, Claude Desktop, any custom client — all speak Private API, all get the same grounded retrieval + citations.

Connect the long tail

Your internal tool speaks Private API but no BeforeQuery connector exists. Point BeforeQuery at the endpoint, describe the schema, and playbooks can read + write against it — no code required.

Federate agents

Multi-agent workflows across teams or vendors, connected via Private API. Each agent stays sovereign; the protocol coordinates.

Answer questions grounded in Private API

Employees and customers ask Private API-related questions in Slack, Teams, or the widget — BeforeQuery answers with the exact Private API record shown alongside the response. No context switching, no "log into Protocol to check" round-trips.

Private API — Frequently Asked Questions

Common questions about connecting BeforeQuery to Private API.

Every compliant client. BeforeQuery's Private API surface is standards-conformant — if your client speaks the spec, it works. No client-specific configuration required.
Standard OAuth 2.0 where Private API supports it, otherwise API-key or bearer-token auth. Credentials are stored encrypted at rest (AES-256-GCM) per workspace, never shared across customers, and rotated on request. The connection is scoped to the least-privilege set of scopes each playbook needs — you approve the scope list on install.
No. Your Private API data feeds only your workspace's own agents and answers. Nothing is used to train a shared model, and nothing crosses workspace boundaries. Bring-your-own-model is available on Enterprise if you want to pin inference to your own OpenAI / Anthropic / self-hosted deployment.
Yes. Every Private API integration is scoped at install time — you pick which resources, users, or record types are visible. You can further restrict per-playbook: a single playbook only touches the specific Private API objects it needs. Scope changes take effect on the next sync.
Every write is logged with the acting user, the playbook that fired it, the exact operation, the target entity IDs, and the timestamp — all in the immutable audit log. Writes are rehearsable in simulation mode against a copy of live data before they touch Private API for real.

Ready to connect Private API?

Start free. No credit card required. Connect your first integration in under 5 minutes.