Agents / API 1.27
Connect OpenAI, Gemini or Perplexity to Bitpont | MCP & REST
Configure Bitpont in OpenAI Responses, Gemini CLI or Perplexity. Test public discovery, choose product tools and use REST with custom clients.
Choose a connection
For hosted tools, use https://www.bitpont.com/api/v1/mcp. Add ?product=treasury to narrow the list. For clients that launch a local process, download the stdio adapter and run it with Node 20 or newer. The tool explorer lists public access and partner scopes.
OpenAI Responses API
Add the following tool definition to the tools array of a Responses request. It exposes discovery and asks for approval. Inspect the returned tool list and tool results. OpenAI MCP documentation.
{"type":"mcp","server_label":"bitpont","server_url":"https://www.bitpont.com/api/v1/mcp","allowed_tools":["bitpont_findTools","bitpont_describeTool"],"require_approval":"always"}Google Gemini CLI
Merge this entry into your Gemini CLI settings. Restart the CLI and run /mcp to inspect Bitpont. Ask it to find public Treasury tools on Base. A Gemini application using function calling can also dispatch selected REST operations itself. Gemini CLI configuration · Gemini function calling.
{"mcpServers":{"bitpont":{"httpUrl":"https://www.bitpont.com/api/v1/mcp?product=treasury"}}}Perplexity remote connector
On a Perplexity account with custom connectors, open Plugins, add a custom MCP connector and enter the HTTPS server URL. Choose the remote HTTP transport and public access for discovery. Ask for the exact Bitpont tool used and its returned workspace URL. Connector availability depends on the client and workspace settings. Perplexity connector setup.
REST and other model hosts
Read the action directory. Let your application dispatch only tools it has selected, validate input against OpenAPI, and return the HTTP response to the model. Keep credentials and signing inside the host. For offline development, use the tested examples and tool catalogue.
Verify the first connection
Call bitpont_treasuryTools with {"network":"base","task":"payments","limit":3}. Inspect items, the next tool and each canonical path. If an HTTP client receives 429, wait for Retry-After. For a supported trade, reuse the private workspace and sign using the authorized wallet. Named partner keys also need the scope specified for the operation. Execution and wallet permissions.