skip to content

the web, remembered.

save sources and research into a living, cited map—what they say, how they connect, and the evidence underneath—ready for you or any agent to recall.

get started
🔍Stripe API Documentation
stripe.com/docsstripe.com/api+1

Comprehensive API documentation covering payment infrastructure, authentication flows, webhooks, and client libraries across 12 programming languages.

2 hours agocomplete

research once. keep what it found.

turn multi-source research into durable, cited webs—not a prose blob that disappears with the tab.

💡key insights
view all →
1Stripe uses progressive disclosure — quickstart guides before exposing full API surface area.
2Authentication via bearer tokens with support for restricted keys and granular permissions.
3Webhook system supports automatic retries with exponential backoff and event deduplication.
+2 more insights

saved sources. still alive.

track pricing, product pages, docs, and changelogs so changes return as cited source receipts instead of going stale.

📊comparison
3 sources
N
notion.so/product
94
C
coda.io/product
88
O
obsidian.md
81

cited context, right when needed.

recall saved webs or pull a small context packet into any agent without repeating the research or losing the sources.

📊comparison
3 sources
N
notion.so/product
94
C
coda.io/product
88
O
obsidian.md
81
🌐entities
browse all →
StripeorgREST APItechOAuth 2.0protocolWebhooksconceptPCI DSSstandardNode.jstech+4 more

open context. no lock-in.

your research stays portable across the web, CLI, MCP, API, and webhooks. Webs keeps it; no agent or chat owns it.

⚡batch analysis
4 URLs · 3 complete
📐linear.appcomplete1.8s
▲vercel.comcomplete2.1s
⚡convex.devcomplete1.4s
🔐clerk.comanalyzing...

for your agents

One endpoint. Seven tools.

Install the npm CLI for yourself. Give agents the instructions below. Both pull living, cited web context from the same durable home.

npm CLI
npm install --global webs
Set up Webs MCP
https://webs.creative-int.com/mcp

Give your agent living, cited web context. Choose its client, copy the native setup, and authorize with OAuth on first use or a token from Connect.

Codex
~/.codex/config.toml
Claude Code
one terminal command
Cursor
.cursor/mcp.json
Windsurf
~/.codeium/mcp_config.json
VS Code
.vscode/mcp.json
Any MCP client
Streamable HTTP initialize
Agent instructionsAGENTS.md
Use Webs over MCP as web-context memory: a durable, living home for cited web content. Webs remembers the web, not the conversation; your agent pulls context from it.

The seven tools:
- `save` — save URLs or supplied content when it should remain recallable.
- `recall` — search saved web context before repeating research; use `webId` for an exact web.
- `context` — request a small, cited packet for the current task and why it matters.
- `ask` — synthesize saved web context when a direct cited answer is useful.
- `watch` — create or list monitors for sources that need recurring attention.
- `run` — start durable research, comparison, or monitor-snapshot work and poll the returned run.
- `readiness` — check authentication, entitlement, and scope before a longer workflow.

Working rhythm:
1. Call `context` at task start when saved web context may help.
2. Call `recall` before fresh research or when prior source work may already cover the task.
3. Use `run` when research should outlast the current thread; poll it to a terminal state.
4. Call `save` for durable URLs, content, and findings that future work should reuse.
5. Use `ask` only when cited synthesis over saved context is useful.
6. Keep citations and source excerpts attached to claims.

the web, remembered.

Webs keeps cited web context durable, living, and portable across the web, CLI, and MCP.

get started