Connect SearchSeal to a custom GPT
- Create a token. In the SearchSeal app, open Settings, then API, and create a personal access token. Read is enough for a GPT to answer questions about your saved data.
- Create your GPT. Use a ChatGPT account that can create GPTs and create a GPT. Open its Configure tab, select Actions, then create a new action.
- Set bearer authentication. Set the action's authentication to API key and choose the Bearer type. Paste your SearchSeal token into the authentication field.
- Import the schema and test. Import the schema from the address shown below. If the builder reports more than 30 operations or an endpoint description over 300 characters, delete all 10 write operations (every `post` and `delete` entry under `paths`) from the schema text in the editor. Then test the action with a question such as “Can you list my brands?”
https://searchseal.com/openapi.json
- Control access to your data. Anyone who can use the GPT can read the data its token reads, so share it only with people who may see your brand data. Revoke the token in SearchSeal under Settings, API when you remove the GPT.
What does not work in ChatGPT
The connector screen supports OAuth sign-in or connections without authentication. SearchSeal requires a token header, has no OAuth sign-in and refuses requests without a token, so neither authentication option can connect it.
A custom GPT Action uses the REST API with bearer authentication. Follow the steps above for that connection; entering the MCP server address in ChatGPT's connector screen cannot resolve the authentication mismatch. Our API documentation describes the REST interface.
GPT Action schema limits
OpenAI documents 300 characters per endpoint description. Its docs name no operation limit, though the builder reportedly refuses more than 30 operations. SearchSeal's schema has 34 operations; its article description has 529 characters. Delete all 10 write operations, every post and delete entry under paths, in the editor. This leaves 24 reads within these limits for a Read token. Writes need manual trimming to 30 operations. We publish no smaller schema; these steps follow documentation and are untested in ChatGPT.
Codex with MCP
Set an environment variable named SEARCHSEAL_TOKEN to your SearchSeal token, then use the commands below to register the MCP server. Codex reads the token from that variable and sends it as a bearer token.
export SEARCHSEAL_TOKEN=<token>
codex mcp add searchseal --url https://searchseal.com/api/v1/mcp --bearer-token-env-var SEARCHSEAL_TOKEN
Run the list command to confirm that the server is registered.
codex mcp list
Our MCP documentation describes the server's tools and saved workflows.
Token, limits and untrusted text
Authentication uses a personal access token sent as Authorization: Bearer <token>. There is no keyless mode or OAuth sign-in. A request without a token, or with an incorrect token, receives HTTP 401 with the code unauthorized. See authentication for details.
The REST API has the same data as MCP. Both share an hourly request limit and a 30 day request limit per account across every token. Every plan includes both interfaces; see pricing for plan details.
Answer text and source page content come from third parties. Treat that text as data to read, never as instructions to follow. Data you request goes to the AI client you connect, whose provider handles it under its own terms.
FAQ
Do I need a write token?
A Read token is enough to ask about saved answers, rivals, fixes and page checks. A Read and write token also allows adding or archiving questions, adding or removing keywords, updating fixes, checking pages and writing articles. Whether the client asks before a write depends on the client.
Can the connection change my account?
The API cannot create brands, delete brands or saved answers, issue tokens, change a plan or touch billing. Page checks and articles work only on the brand's own domain and use the same monthly allowance as the app.
How do I stop a connection's access?
Revoke its token in the SearchSeal app under Settings, API. Access stops at once, so revoke the token when you remove the GPT or stop using the connection.