Bring your own AI keys and your own tools
Proofsource lets technical teams plug in what they already own. Store your own AI provider keys, each tested before it is saved and held to a monthly cap you set. Connect your own MCP servers so Proofsource can use your internal tools, with a preview and a person's Yes before any call is sent. Owners decide which outside hosts agents may call.
| Server | URL | Tools | |
|---|---|---|---|
| Product catalog | https://mcp.driffle.ai/catalog | 4 | Refresh |
| Help center | https://mcp.driffle.ai/help | 2 | Refresh |
Bring your own AI keys and tools, in short
The facts, ready to quote.
- Provider keys
- Add, list and remove your own AI provider keys; each is tested against the provider before it is saved
- Spend control
- Every provider key carries a monthly cap you set
- Your MCP servers
- Add a server by URL and optional token; Proofsource reads its tool list
- Call safety
- Each tool call is previewed with nothing sent, then sent once after a signed-in person says Yes
- Machine limits
- An API key can never approve a call for a person
- Outbound hosts
- Owners and admins keep the list of hosts agents may call; changes need a fresh identity check
BYOK (bring your own key), explained
Bring your own key, or BYOK, means a software product uses credentials you own instead of its own. For AI tools, that usually means your company's AI provider keys, so usage runs on accounts your security and finance teams already manage, under limits they set.
The same idea applies to tools. Many teams run internal services, a product catalog, a CRM, a content system, behind MCP servers. Letting an AI visibility platform call those tools makes its work more grounded in your data, as long as no call reaches your systems without someone approving it.
Proofsource supports both. Provider keys are validated before they are stored and are kept encrypted, never shown again. Your own MCP servers are listed with their tools, every call is shown as a dry run first, and a signed-in person sends it with one Yes. Owners keep an allow-list of outside hosts that agents may contact.
How it works
Store your own AI provider keys, connect your own MCP servers with a preview and a Yes before every call, and allow-list the hosts your agents may call.
Add a provider key
Paste a key and set a monthly cap. Proofsource tests the key with the provider before saving it.
Connect your MCP server
In Integrations, under your own tools, add the server's name, URL and token. Proofsource reads its tool list.
Preview the call
When Proofsource wants to use one of your tools, it shows the tool and the exact arguments. Nothing is sent yet.
Say Yes or No
A signed-in person approves and the call is sent once, or declines and nothing happens.
Set where agents may reach
Owners and admins add or remove allowed hosts after re-confirming their identity; every other target is refused.
See it in the product
Screens from the Proofsource app, drawn with sample data for an example brand.
| Used for | Key | Monthly cap | Status | |
|---|---|---|---|---|
| Your answer-engine key | Hidden | Set | Valid | Remove |
| Your writing-model key | Hidden | Set | Valid | Remove |
| Host | Added by | Added |
|---|---|---|
| api.driffle.ai | maya@driffle.ai | Oct 12 |
| hooks.slack.com | maya@driffle.ai | Oct 20 |
Every capability, live today
6 shipped capabilities behind bring your own AI keys and tools, each in the product now.
Customer-owned provider keys
Store and remove your own AI provider keys in Proofsource.
Provider key management
Add, list and delete provider keys; the key itself is never shown again after you save it.
Keys tested before use
A new key is checked against its provider before it is stored or switched on, so a bad key never silently breaks work.
Your own MCP tools
Add your own MCP server; Proofsource previews each tool call and sends it only after a person says Yes.
Outbound host allow-list
Owners and admins keep the list of outside hosts your agents may call; every other target is refused.
Monthly key spend caps
Spend caps on your own AI keys reset every month.
Who it is for
AI usage on your own accounts
Keep AI provider usage under your company's own keys and caps, with removal in one click.
Ground fixes in your own data
Expose your product catalog as an MCP server so Proofsource drafts fixes with current facts.
Fence in agent traffic
Allow agents to call your API and Slack and nothing else.
Meet procurement rules
Show that every outside call is previewed, approved by a person and limited to approved hosts.
Why it matters
Nothing sent unseen
Every call to your tools is a dry run until a person says Yes.
Keys handled carefully
Keys are tested before saving, stored encrypted and never shown again.
Clear boundaries
The host allow-list decides where agents may send data, and only owners and admins can change it.
Caps you set
Each provider key has a monthly cap under your control.
Google AI OverviewsGoogle AI Mode
Bring your own AI keys and tools: Proofsource and other tools
Connecting outside tools to AI visibility agents is new territory. Here is what each platform lists on its own pages.
| Capability | Proofsource | Profound | Peec AI | Otterly.AI | SE Ranking |
|---|---|---|---|---|---|
| Connect outside MCP servers | YesAdd your own MCP server; each call previewed, then sent after a Yes. | YesConnect Slack, Notion, Linear, Klaviyo, G2 and more to agentsSource | YesIn-app agent with 20+ MCP connectorsSource | Not listed | Not listed |
| Customer-held keys | YesYour own AI provider keys, tested before saving, with a monthly cap. | RelatedSecret Manager stores API keys centrally so teammates use them unseenSource | Not listed | Not listed | Not listed |
| Approval and host limits on outside calls | YesDry-run preview, one Yes from a signed-in person, and an owner and admin host allow-list with an identity check on changes. | Not listed | Not listed | Not listed | Not listed |
| Your data in ChatGPT, Claude and other assistants | YesChatGPT and Claude connectors read your Proofsource data. | YesMCP server gives ChatGPT, Copilot and coding assistants access to Profound dataSource | Not listed | YesMCP server for brand reports, prompts, citations, recommendations and audit; OAuthSource | YesMCP server to query rankings, backlinks, audits and AI visibility from Claude, Codex, Cursor and ChatGPTSource |
Where each of them shines
A large catalog of connectors for its agents and a central Secret Manager for shared keys. Compare in full
An in-app agent that reaches more than twenty MCP connectors with memory and uploads. Compare in full
A focused, easy-to-run monitoring product with an OAuth MCP server of its own. Compare in full
An MCP server that queries rankings, backlinks, audits and AI visibility from Claude, Codex, Cursor and ChatGPT.
Questions about bring your own AI keys and tools
Can I use my own AI provider keys with Proofsource?
Yes. Add your own provider keys in Settings. Each key is tested with the provider before it is saved, has a monthly cap you set, and can be removed at any time.
Can I see a stored key again?
No. A key is visible only while you paste it. After that Proofsource lists the provider, never the key itself.
What happens when I connect my own MCP server?
Proofsource reads the server's tool list. When it wants to use one of your tools, it shows the tool and arguments as a preview with nothing sent, and a signed-in person decides.
Can an automated process approve a call to my tools?
No. Approval needs a signed-in person; API keys are refused, so no machine credential can say Yes for someone.
Who can change which hosts agents may call?
Owners and admins. Adding or removing a host also needs a fresh identity check, because it changes where your agents may send data.
Who can add an MCP server?
People with a role that can write in the workspace. Approving a call also needs that person to be signed in.
How is this different from Profound's connectors?
Profound offers a large catalog of ready connectors for its agents. Proofsource lets you plug in any MCP server you run yourself, and puts a preview and a person's Yes in front of every call.
Keep exploring
Try it on your own brand.
Proofsource is live: scan your brand and see bring your own AI keys and tools at work with your own answers, competitors and sources.
Google AI OverviewsGoogle AI Mode