Ceramic for AI agents

Ceramic Search returns relevant public web content for a keyword query, giving an agent a lexical search layer built for AI use rather than a browser. 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.

Connect Ceramic See the 1 actions ↓

Web data and scrapingAPI keyMCP + REST

AUDIT LOG · CERAMICPOLICY: acme-support

09:41:07 · claude · u_8f2read

ceramic.search_web

Search Web✓ allowed · 212ms

EVERY CERAMIC CALL, ON THE RECORD

01 · USE CASES

What agents do in Ceramic.

Search the web for a topic

Search the public web for a keyword or question and get back relevant pages to cite.

Research a company mention

Search for recent public mentions of a company before drafting an outreach note.

Gather sources for a summary

Pull several relevant web results on a topic to compare before writing a summary.

02 · ACTIONS

1 Ceramic actions, graded by risk.

Every Ceramic action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

Look things up. Allowed by default.

ceramic.search_web
Search Web

write

Create and change things. Allow, or ask the user first.

No write actions.

destructive

Delete, cancel or archive. Ask first, or deny outright.

No destructive actions.

03 · HOW IT WORKS

Ceramic in three steps.

01Your users connect CeramicThey add their Ceramic 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 Ceramic through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.

POLICY.TS

await arc0.policies.set('ceramic', {
  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

04 · AUTH AND DATA

How Ceramic connects.

Users add their Ceramic 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 Ceramic 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

05 · WORKS WITH

Use Ceramic from any agent.

Claude

ChatGPT

Cursor

Codex

VS Code

OpenAI Agents SDK

Claude Agent SDK

Vercel AI SDK

Mastra

LangGraph

06 · RELATED

More web data and scraping apps.

Just One API288 actions

Apify183 actions

ALL WEB DATA AND SCRAPING APPS →

07 · FAQ

Ceramic and Arc0, answered.

Q01

Can I use Ceramic with Claude, ChatGPT or Cursor?

Yes. Connect Ceramic 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 Ceramic actions you allow.

Q02

How do users connect Ceramic?

Users add their Ceramic 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.

Q03

Which Ceramic actions can my agent take?

1 in total: 1 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Ceramic?

Yes. Allow read actions and deny writes in the Ceramic policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Ceramic too?

Yes. The same Ceramic connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Ceramic into your agent.

Your users connect Ceramic once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.

Connect Ceramic Browse all apps →

Free to build · MCP + REST · Audit log on every plan