disburse / docs

Connect ChatGPT

You can use disburse inside ChatGPT as a Custom GPT Action: ChatGPT calls the disburse REST API directly from an OpenAPI spec we publish, authenticated with your API key. Natural-language queries work out of the box: ChatGPT sends the text and disburse parses it into filters server-side.

Custom GPTs require a ChatGPT Plus, Team, or Enterprise plan.

What you need

  • A disburse API key (sk_live_…) from your dashboard.
  • The published OpenAPI spec URL: /openapi.json on your web app (e.g. https://app.disburse.dev/openapi.json).

Set it up

  1. In ChatGPT, open Explore GPTs → Create, then the Configure tab.
  2. Scroll to Actions and click Create new action.
  3. Under Schema, click Import from URL and paste your /openapi.json URL. ChatGPT loads the operations (search_people, search_companies, enrich_*, verify_*).
  4. Under Authentication, choose API Key, set Auth Type to Bearer, and paste your sk_live_… key.
  5. Save. Test it with a prompt like "Find fintech CFOs in Sydney" or "Enrich sarah@acme.com".

How it works

ChatGPT never sees the filter schema; it just sends your words to the API:

text
You: "heads of growth at Series B fintechs in Australia"
      │
      ▼  ChatGPT calls POST /v1/search/people { "query": "..." }
   disburse parses the text into filters, runs the search, returns results

That's the same natural-language path the API and the MCP connector use; disburse does the parsing, so any client that can send JSON works.

ChatGPT vs. the MCP connector

Both let an assistant use disburse; they differ in transport and auth:

Custom GPT Action (this page)MCP connector
TransportREST API (/v1/*) via OpenAPIMCP tools (/mcp)
AuthAPI key (Bearer)OAuth or API key
Best forChatGPTClaude and other MCP clients

Troubleshooting

  • Import fails / schema errors: ChatGPT's importer is strict about OpenAPI 3.1. If it rejects the spec, re-import or paste the JSON directly.
  • 401 Unauthorized: the key is missing or wrong; re-check the Bearer key in the action's Authentication settings.
  • Calls hit the wrong environment: the servers URL baked into /openapi.json decides which API is called. Confirm it points at the environment your key belongs to.