Your software.The same safeguards.

Bring Zeopilot’s website intelligence into your software—with scoped access and the same safeguards.Website intelligence. Built into your tools.

Explore the API View OpenAPI contract

Private betaRead-only firstScoped by website

Useful connections. Clear boundaries.

Less switching tools.
More shared understanding.

Help your team see the same website status, incident context and evidence—where they already work. Start with a small, approved integration rather than handing over the keys.

Agency dashboards

Bring authorized websites into a portfolio view, with recorded status and observation time beside every result.

Service operations

Give an approved support tool the incident context needed to understand a problem, without private customer data.

Evidence-led reporting

Put proposal and evidence summaries next to a business decision. Reading a recommendation never grants approval.

Explore without a token

See the shape
of a safer integration.

Choose an operation. Inspect the scoped request and a clearly labeled example response. Everything here runs locally in your browser; no live access is provisioned.

GET /api/v1/websiteswebsites:read

Build a portfolio view using only the websites explicitly included in your grant.

{
  "requestId": "5f7f4bf4-3b64-4c80-8d91-21587753f2e8",
  "version": "1-beta",
  "source": "fixture",
  "observedAt": "2026-10-12T09:00:00Z",
  "readOnly": true,
  "data": [
    {
      "id": "site_example",
      "name": "Evergreen — example",
      "url": "https://evergreen.example",
      "status": "review_pending",
      "observedAt": "2026-10-12T09:00:00Z"
    }
  ],
  "pagination": {
    "offset": 0,
    "limit": 20,
    "nextOffset": null
  }
}

Interactive contract example. Synthetic records only. This explorer sends no API requests and accepts no credentials.

What the beta can expose

Owner-reviewed website exports, incident summaries, proposal summaries, evidence and event records. Responses are bounded, permission-checked and audited. This is not a real-time database connection.

What stays out of reach

Publishing, customer approvals, billing and unrestricted investigations. Credentials are provisioned privately. Delegated OAuth onboarding and automated outbound delivery are not activated by this page.

Start narrow.
Earn deeper access.

A partner integration should have an explicit purpose, an authorized website list and a clear way to revoke access. Evidence comes before expansion.

01Define the jobAgree on the dashboard, report or support workflow and the information it actually needs.
02Scope the grantLimit access to an approved workspace, website list and read-only scopes.
03Verify the boundaryTest permission failures, expiration, revocation and safe handling of repeated events.
04Review togetherValidate the integration with approved exports before authorizing live customer access.

Your tools. Your authority.

The same separation of proposals, verification and approval protects every integration. Access remains disabled until explicitly provisioned.

Explore the safeguards