EQALL + your AI agents.
Give your own AI agents and apps what EQALL knows: who your contacts are and how to talk to them, the companies you sell to, and prep and recaps for every meeting. Connect over MCP or call the REST API.
What you can do
EQALL exposes the same intelligence you see in the app to agents and applications you control, such as Claude, Cursor, a custom agent, or your own scripts.
| Area | What you get |
|---|---|
| Contacts | Find people in your network, their profile, talking points, how to communicate with them, and your last meeting recap. Add new contacts. |
| Companies | Find companies you work with, their overview, products, partners, leadership, finance (public companies), insights tailored to what you sell, and news. |
| Meetings | Search past and upcoming meetings, including external-only. Get prep (agenda, talk tracks, personas, company background) and recaps (summary, action items, risks, deal intelligence). |
AI agents connect to the MCP server and discover the tools on their own. Apps and scripts use the REST API, which offers the same operations.
Your permissions carry over. A key or connected AI tool acts as the person who created it and sees only what they can see in EQALL: their network, the companies they work with, and meetings they're invited to.
Get an API Key
In EQALL, go to Settings → Integrations → API & AI agents. If you don't see it, API access has been turned off for your company; ask your company admin.
Give it a name you'll recognize, such as "Sales agent". Turn on Allow adding contacts only if the agent needs to create contacts. Otherwise the key is read-only.
Click Create API Key and copy it. It starts with eqk_ and is shown only once. If you lose it, revoke it and create another.
| Permission | Allows |
|---|---|
read Always | Every search and details operation |
write:contacts | Adding contacts |
Send the key on every request as Authorization: Bearer eqk_…. Check that it works:
curl https://api.eqall.com/external/whoami \
-H "Authorization: Bearer $EQALL_KEY"Treat keys like passwords. Keep them out of source code and shared documents. Revoking a key from Settings → Integrations → API & AI agents stops it working immediately. Each user can have up to 10 active keys.
Connect an AI Agent (MCP)
EQALL runs a Model Context Protocol server at https://api.eqall.com/mcp (Streamable HTTP, no sessions). Point any MCP client at it with your key as a bearer token.
claude mcp add --transport http eqall https://api.eqall.com/mcp \
--header "Authorization: Bearer eqk_your_key_here"{
"mcpServers": {
"eqall": {
"url": "https://api.eqall.com/mcp",
"headers": { "Authorization": "Bearer eqk_your_key_here" }
}
}
}Claude API or the Agent SDK: register a remote MCP server with URL https://api.eqall.com/mcp and use your API key as its authorization token.
Once connected, ask something like "Prep me for my next meeting with Acme". The agent chains findMeetings, getMeetingDetails and getContactDetails on its own.
Using claude.ai or ChatGPT? You don't need a key. Add EQALL as a connector and sign in. See Connect Claude or ChatGPT.
Calling MCP directly
Any HTTP client can POST JSON-RPC 2.0 messages. No initialize call is needed. The response arrives as one server-sent event, and the tool result is JSON text in result.content[0].text.
curl https://api.eqall.com/mcp \
-H "Authorization: Bearer $EQALL_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"findContact","arguments":{"query":"jane acme"}}}'Connect Claude or ChatGPT
AI tools that support connectors, such as claude.ai, the Claude apps and ChatGPT, connect with EQALL sign-in instead of an API key. You approve the connection once, and the tool never sees your password.
In Claude, open Settings → Connectors → Add custom connector. In ChatGPT, add a custom connector from Settings → Apps & Connectors (some plans require developer mode or an admin to allow custom connectors). Use this URL:
https://api.eqall.com/mcpClick Connect. A window opens on eqall.com. Sign in if you aren't already.
EQALL shows which tool is asking and what it can do. Check you're signed in as the right person, then click Allow. The tool can now use the EQALL tools in any conversation.
Claude Code can sign in the same way. Add the server without a header, then run /mcp and choose Authenticate:
claude mcp add --transport http eqall https://api.eqall.com/mcp| Good to know | |
|---|---|
| Permissions | Connected tools can read (read). Tools that also ask for write:contacts can add contacts. |
| Staying connected | Access renews automatically while you keep using the tool. Unused connections expire after 30 days, and you sign in again. |
| Disconnecting | See and disconnect tools under Settings → Integrations → API & AI agents → Connected AI Tools. Access stops immediately. |
| Company control | If your company turns off API & AI agent access, connected tools stop working and new connections are refused. |
Building your own MCP client?
EQALL follows the MCP authorization spec (OAuth 2.1). An unauthenticated request to /mcp returns 401 with a WWW-Authenticate header pointing to https://api.eqall.com/.well-known/oauth-protected-resource. From there, discover the authorization server (/.well-known/oauth-authorization-server), register with Dynamic Client Registration, and use the authorization code flow with PKCE (S256) and resource=https://api.eqall.com/mcp. Callback URLs must use https, or http on localhost.
Tools
Agents get each tool's description and input schema from tools/list.
| Tool | What it does |
|---|---|
findContact | Search your network by name, email or company. Every word must match, so "jane acme" finds Jane at Acme. |
getContactDetails | Profile, work history, talking points, communication style and last meeting recap. |
createContact write:contacts | Add a person to your network. EQALL creates them and their company from the email domain if they're new. |
findCompany | Search the companies you work with, by name or domain. |
getCompanyDetails | Overview, LinkedIn, addresses, products, partners, leadership, finance, insights and news. |
findMeetings | Search past, in-progress and upcoming meetings by title, attendee, company, dates, and external or internal. |
getMeetingDetails | Meeting data and attendees, plus prep (agenda, talk tracks) and/or recap (summary, action items, deal intelligence). |
REST API
The same operations as plain JSON over HTTPS at https://api.eqall.com. Every parameter and response field, with examples, is in the API & MCP Reference.
| Endpoint | Purpose |
|---|---|
GET/external/whoami | Check a key |
GET/external/contacts?query= | Search contacts |
GET/external/contacts/{contactId} | Contact details |
POST/external/contacts | Add a contact: { "firstName", "lastName", "email" } |
GET/external/companies?query= | Search companies |
GET/external/companies/{companyId} | Company details |
GET/external/meetings | Search meetings |
GET/external/meetings/{meetingId} | Meeting details. Add ?include=prep,recap for those parts. |
curl -X POST https://api.eqall.com/external/contacts \
-H "Authorization: Bearer $EQALL_KEY" -H "Content-Type: application/json" \
-d '{"firstName":"Jane","lastName":"Doe","email":"jane.doe@acme.com"}'Meeting Search & Details
All search filters are optional and can be combined. With none, you get meetings within 30 days of today.
| Filter | Meaning |
|---|---|
title, attendee, company | Fuzzy match on the meeting title, an attendee's name, or a company that attended |
from, to | Date range. YYYY-MM-DD means whole days in your timezone. |
when | past (most recent first), upcoming (soonest first) or all |
type | external: someone from outside your company attended. internal: only colleagues. all is the default. |
curl "https://api.eqall.com/external/meetings?type=external&from=2026-09-01&to=2026-09-30" \
-H "Authorization: Bearer $EQALL_KEY"Meeting details always include the meeting itself and its attendees. Attendees also include anyone who spoke without being invited, and once there's a transcript, each person's sentiment, advocacy and engagement. Use include to add:
Sensible defaults: upcoming meetings return prep and completed meetings return recap. The first prep request can take a few seconds while EQALL builds the agenda. After that it's cached.
IDs, Paging & Errors
IDs. contactId, companyId and meetingId are UUIDs. Pass the IDs one call returns into the next.
Paging. Search results come back as { "meetings": [...], "nextCursor": "…" }. Pass nextCursor back as cursor for the next page. null means there are no more. limit sets the page size: 20 by default, 50 at most.
Access. Anything outside your network, or a meeting you weren't invited to, returns 404, the same response as for an ID that doesn't exist.
| Status | Meaning |
|---|---|
400 | Malformed ID or cursor |
401 | Missing, unknown or revoked key |
403 | The key lacks a permission, e.g. write:contacts |
404 | Not found, or not visible to you |
422 | Invalid parameters. The message lists each problem. |
429 | Over 60 requests per minute for this key. Wait and retry. |
Over MCP, the same failures come back as a tool result with isError: true and a short message, so the agent can react.
Setup Checklist
- API key created in Settings → Integrations → API & AI agents, read-only unless the agent adds contacts
- Key stored securely, not in source code or shared documents
/external/whoamireturns your name and company- MCP client pointed at
https://api.eqall.com/mcpwith the key as a bearer token, or Claude / ChatGPT connected by signing in - Agent can list the 7 EQALL tools
- Postman collection imported for manual testing (optional)
Talk to our team.
Tell us what your agent needs to do. We'll help you connect it to EQALL, or add the tools you're missing.
