Developer portalPublished source contracts; production access is gated

One front desk. Two ways to build on it.

Use the Client API when software needs stable business records. Use MCP when an AI agent needs bounded tools and reviewable actions. Both surfaces preserve the same customer, permission, and product boundaries.

Review-gated source contract

For software and CRMs

Client API

A 78-operation OAuth source contract for approved integrations. It provides tenant-scoped reads plus operation-specific, narrowly scoped writes. Production access remains gated.

  • 78 operations
  • One business per OAuth grant
  • Authenticated OpenAPI 3.1 contract
Read the API reference
Deployment-gated read/write contract

For ChatGPT and AI agents

MCP

The public OAuth source contract includes 46 bounded reads and 46 reviewed write tools. Each connection exposes only its permitted tools. Signature tools record approval under an owner-created delegation, but never send or sign a document.

  • 92 OAuth tools: 46 read, 46 write
  • OAuth with PKCE and resource binding
  • No separate MCP price
Read the MCP reference
Zapier v1.0.1Private draft documented

The reviewer-ready contract for the private Zapier integration, including OAuth, all 10 visible operations, REST hook lifecycle, examples, errors, and retry safety.

  • 5 REST hook triggers
  • 3 create actions and 2 searches
  • 8 narrow OAuth scopes
Read the Zapier reference

Different interface, same guardrails.

API and MCP are two doors into the same product, not two separate versions of First AI Employee.

01The customer is derived from the OAuth grant, never supplied by the caller.

02MCP consent is owner-only. Client API consent uses the signed-in customer role allowed for each scope; exports remain owner-only. Connections can be revoked from Connected Apps.

03Paid capabilities keep the same published account entitlements and allowances across channels.

04Compatible MCP publishers can use validated HTTPS client metadata. Client API and unusual fixed-client registrations are reviewed.

Building an integration?

A business owner can connect a compatible MCP client without a developer account. Client API access requires a developer account, application review, operator provisioning, and customer consent. The owner-created service-account backend is MCP-only and read-only, and it does not yet have a customer dashboard screen.

Create developer accountSign in

Compatible MCP clients connect through self-service. Client API applications and unusual fixed MCP clients still require review.

Submit a manual access request instead
What are you trying to do?
Is the business already a First AI Employee customer?
Access request details

For example, ChatGPT. If you have not chosen one, say that.

Describe the first useful workflow. Do not include customer records, caller details, or other personal data.

Minimum scopes needed

Choose only the scopes required for the first workflow. Paid capabilities still require the matching product entitlement.

MCP scopes

Explain where retrieved data will go, who can access it, and when it will be deleted.

The person or monitored address we should contact about security or privacy issues.

Tell us when you hope to connect and whether a customer decision depends on it.

Do not submit passwords, access tokens, API keys, client secrets, customer IDs, or customer data. This request does not issue credentials or enable access.