Developers

Read your reviews and numbers from your own dashboards, spreadsheets and tools.

Claude, ChatGPT and other AI assistants

Seyclops has a connector (an MCP server) so an owner can ask their AI assistant about their reviews and have it write reply drafts. Connector address:

https://seyclops.com/mcp

Claude: Seyclops is in Claude's connector directory: open it and click Connect. (Or Settings → Connectors → Add custom connector and paste the address.)
ChatGPT: Settings → Apps & Connectors → Create (Developer mode, on plans that offer custom connectors), paste the address, choose OAuth, click Connect.
Sign in to Seyclops, pick the business, tick what the assistant may do, and click Allow.

Tool	Permission	What it does
`get_reputation_summary`	analytics:read	Rating, reviews, replies owed, score and the top thing to fix.
`get_analytics`	analytics:read	Reply rate, request funnel, channels, rating mix, 12 weeks of reviews.
`list_reviews`	reviews:read	Reviews with replies; filter to the ones that need an answer.
`list_review_requests`	requests:read	Requests and their status, without phone numbers or emails.
`draft_review_reply`	reviews:draft (Pro)	Saves a reply draft. Never publishes.
`create_review_request`	requests:create (Pro)	Prepares a request in Ready to send. Never sends.

What an assistant can never do: publish a reply, send a text or email, see customers' phone numbers or emails through these tools, or touch billing and settings. The owner approves and sends everything in Seyclops. Starter plans connect read-only.

Sign-in uses OAuth 2.1 with PKCE and dynamic client registration. Access tokens last an hour; refresh tokens rotate, and reusing an old one ends the connection. Owners see every connected assistant and its recent activity in Integrations, and can disconnect it there at once. Developer tools that can't do OAuth (for example Claude Code) can use a read-only API key as the bearer token instead.

The Seyclops API

A read-only API for one business at a time. It is part of the Pro plan and the free trial.

In Seyclops, open Integrations → Developers and AI assistants → API access.
Name the key, tick what it may read, and click Create key. Copy it: it is shown once.
Send it in the Authorization header on every call.

curl -H "Authorization: Bearer YOUR_KEY" https://seyclops.com/api/v1/summary

Endpoints

Call	Permission	Returns
`GET /api/v1`	any	The business, the key's permissions and the endpoint list.
`GET /api/v1/summary`	analytics:read	Rating, review count, reviews in the last 90 days, replies owed, reviews won, reputation score and grade, top recommendation.
`GET /api/v1/analytics`	analytics:read	Reply rate, the request funnel (last 90 days), channels, rating mix and 12 weeks of reviews.
`GET /api/v1/reviews`	reviews:read	Reviews, newest first, with any reply. `?status=needs_reply\|replied\|low`, `?limit=` (up to 100), `?offset=`.
`GET /api/v1/requests`	requests:read	Review requests: customer name, channel, job and status. Never phone numbers or emails.

Limits and errors

Up to 600 calls an hour per key. Over that: 429 with a Retry-After header.
401 missing or wrong key · 402 the plan doesn't include the API · 403 the key lacks that permission, or its creator no longer has access.
Errors are JSON: {"error": "..."}.

Security

Keys are read-only, see only the business they were made in, and act as the person who made them: if that person leaves the team, the key stops working.
Seyclops stores only a fingerprint (hash) of each key, so keys can't be read back, even by us. Lost one? Revoke it and make another.
Keys work only in a header, never in a link. Every call is logged, and the latest show in Integrations.

Job software webhook

To send review requests automatically when a job is finished, use the job webhook instead. Its setup, with steps for Jobber, Housecall Pro, ServiceTitan, Zapier and Make, is in Integrations → Connect your job software.