REST API vs the MCP endpoint

Crispy has two HTTP surfaces that expose the same tools. Pick based on your client, not on capability, because both run through the same executor.

The MCP endpoint (/api/mcp)

Speaks JSON-RPC. Two methods matter: tools/list returns every available tool with its input schema, and tools/call executes one:

curl -X POST https://crispy.sh/api/mcp -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_people","arguments":{"keyword":"VP Engineering","limit":5}}}'

Use it when your client is an MCP host (Claude, Cursor, n8n's MCP Client node) or when you want the entire tool surface behind one endpoint.

The REST API (/api/v1/)

28 curated endpoints with conventional GET/POST/PATCH/DELETE semantics and an OpenAPI 3.1 spec at /api/v1/openapi.json. Use it when you want typed paths, generated SDKs, or an API your team can read in Postman.

Same behavior, both doors

Rate limits, safety checks, and validation are identical. An invitation sent over REST counts against the same daily budget as one sent through Claude. Your API key works on both, with the same Authorization: Bearer header.

One thing that no longer exists

The raw LinkedIn passthrough endpoint at /api/v1/raw was retired and now returns 410 Gone. There is no direct replacement, and that is deliberate: use the dedicated typed endpoints for profiles, messaging, network, and search instead. They carry the validation and safety checks the raw passthrough could not.