Fairing for AI agents
Fairing runs post-purchase attribution surveys, helping ecommerce teams learn how customers found them and measure marketing performance beyond what ad platforms report on their own. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Fairing.
Pull survey responses
List responses to a post-purchase survey to analyze which channels are driving orders.
Check a survey's questions
List the questions on a survey to confirm it matches what marketing wants to measure.
Read-only response reporting
Keep response and question lookups read-only, since this connection only reports on survey data.
2 Fairing actions, graded by risk.
Every Fairing action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- fairing.list_questionsList Questions
- fairing.list_responsesList Responses
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Fairing in three steps.
- 01Your users connect FairingThey add their Fairing api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Fairing through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('fairing', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Fairing connects.
Users add their Fairing api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Fairing connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Fairing from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Fairing and Arc0, answered.
Can I use Fairing with Claude, ChatGPT or Cursor?
Yes. Connect Fairing to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Fairing actions you allow.
How do users connect Fairing?
Users add their Fairing api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Fairing actions can my agent take?
2 in total: 2 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Fairing?
Yes. Allow read actions and deny writes in the Fairing policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Fairing too?
Yes. The same Fairing connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Fairing into your agent.
Your users connect Fairing once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan