SHIFT for AI Agents
How to connect
Choose the integration that fits your stack — from raw HTTP to natural language, with no-code MCP in between.
REST API
Direct HTTP calls to the SHIFT platform. Works with any language or framework. Full OpenAPI 3.1 spec available at /api/v1/docs.
- JSON over HTTPS — no SDK required
- OpenAPI 3.1 spec with interactive playground
- Versioned endpoints — no breaking changes
- Scoped API keys — sent as a Bearer token or X-Shift-API-Key header
MCP Server
Add the SHIFT MCP server as a custom connector in Claude or ChatGPT and book appointments through natural conversation — no config files, no code.
- 28 tools across four access tiers
- Works with any MCP-compatible agent
- Public tools work with no key — sign in from the chat for more
- Auto-discovery of professionals and availability
Google A2A
Full agent-to-agent protocol handshake following the Google A2A specification. Launching when the spec reaches v1.0.
- Standardised A2A capability exchange
- Agent identity verification
- Cross-platform agent interoperability
- Tracking Google A2A v1.0 GA date
How it works
From setup to confirmed booking in three steps.
Get your API key
Sign in as a professional, navigate to Integrations → API Keys, and generate a key with the scopes you need. Read-only keys for discovery, write-enabled keys for booking creation. Using an MCP connector? Skip this and just sign in from the chat.
Choose your integration
Use the REST API for custom code in any language, or add the MCP server as a custom connector in Claude or ChatGPT for instant natural-language booking — no code, no config files.
Your agent books
The agent searches professionals by specialty, checks real-time availability, and creates a confirmed booking on behalf of your user — with full audit trail and in-dashboard labelling.
What agents can do
28 exposed tools across four access tiers cover the full booking lifecycle — from public search to authenticated schedule management.
Built with trust by default
Every layer of the agent API is designed around the assumption that keys will be distributed and credentials will leak — and plans accordingly.
Dual authentication
Every API call carries both an API key (app identity — who is calling) and optionally a Firebase ID token (user consent — on whose behalf). Bookings created by agents are clearly labelled by source.
SHA-256 hashed storage
API keys are stored as SHA-256 hashes — never in plaintext. Even a database breach exposes nothing usable. Keys are shown only once at generation time.
Scope-limited keys
Generate read-only keys for discovery and search, or write-enabled keys that can create bookings. Principle of least privilege baked into the key model.
10-key maximum per account
Each professional account supports up to ten API keys, each independently revocable. Rotate credentials without downtime by generating the new key before revoking the old one.
Agent-created bookings are labelled by source in the professional dashboard, giving professionals full visibility into how bookings were initiated.
Ready to build?
Generate your first API key from the Integrations dashboard and start connecting agents to the SHIFT network today.