Using the REST API directly

If your tool does not speak MCP, you have two HTTP options: the MCP endpoint itself (JSON-RPC) or the typed REST API at /api/v1/.

Option 1: JSON-RPC to the MCP endpoint

The MCP endpoint at https://crispy.sh/api/mcp speaks JSON-RPC over plain HTTP. List the available tools:

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/list"}'

Call a tool with method tools/call, passing name and arguments in params. Example: name 'search_people' with arguments like keyword 'VP Engineering' and limit 5.

Option 2: typed REST endpoints

Crispy also exposes 28 curated REST endpoints at /api/v1/, like GET /api/v1/campaigns or POST /api/v1/search/people. They run through the same executor as the MCP tools, so behavior is identical. The OpenAPI 3.1 spec at /api/v1/openapi.json documents every path and schema. See the REST API help category for authentication, rate limits, and preview mode.

Which to pick

• JSON-RPC if you want the full tool surface behind one endpoint
• REST if you want typed paths, an OpenAPI spec to import, and conventional GET/POST/PATCH/DELETE semantics

Both use the same API key in the same header: Authorization: Bearer YOUR_API_KEY. Rate limits and safety checks apply equally to both.