Notion through Squiid

What Notion is

Notion's API exposes pages, blocks and databases. Databases can be queried with filters and sorts, pages created with structured properties, and block content read or appended, which means a Notion workspace can act as a lightweight content store, a task tracker or a knowledge base that an application reads from. Integrations are granted access page by page, so the blast radius is whatever you explicitly shared. Rate limits are modest and content is paginated, so bulk reads are a background job rather than a request-time call.

For AI-coded products this is usually a knowledge or reporting integration. Pulling internal documentation into a retrieval pipeline so a support assistant answers from it, writing a weekly summary page from product data, creating a task when a customer reports a bug, or maintaining a content calendar that an agent reads before drafting. It is also where a lot of teams keep the specification the agent is supposedly implementing. Keeping the spec in Notion and reading it through the gateway means the agent works from the same source the team edits.

Why connect it through Squiid

Notion is a connect service on Squiid. You link the workspace you already have through the standard OAuth flow and choose what the integration can see, then Squiid holds the token and issues scoped access through https://api.squiid.io/v1/notion/... with Authorization: Bearer $SQUIID_API_KEY, with the official client working by base URL swap (gateway convention). Your Notion plan is billed by Notion directly at the provider's listed price, and the connection can be revoked without touching the workspace itself. Notion's block model is granular, so writing a formatted page means constructing blocks rather than sending markdown.

• One account, one key, one bill, one dashboard. Notion sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Notion credentials. Your code carries SQUIID_API_KEY, so NOTION_API_KEY, NOTION_TOKEN, NOTION_DATABASE_ID never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Notion costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Your existing Notion workspace connected, not replaced
• Database queries with filters and sorts
• Page and block creation and updates
• Page-level access scoping you control
• Notion seats stay billed by Notion

How to connect Notion

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces NOTION_API_KEY, NOTION_TOKEN, NOTION_DATABASE_ID
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/notion/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Notion bills your workspace plan directly at the provider's listed price, with no Squiid margin. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Notion usage, with no markup and no per-request margin.

Notion has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Notion usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Your own account: the Notion account was always yours and Squiid only holds an authorised connection, so revoking it leaves nothing behind. Squiid never owns your code, your schema or your domain, and the gateway speaks Notion's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Notion through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Notion usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.