Default plans, limits, and what's included

Default plans don’t lock features in the Default app: every workspace can use every generally available feature, and enrichment use is measured in credits. This page lists what the product itself counts and limits. Plan names, prices, and included amounts are on the Default pricing page.

How plans work in Default

Features aren’t gated by plan. Nothing in the Default app turns a feature on or off based on the plan a workspace is on.
Some features turn on per workspace while they roll out. These docs mark them “Beta” or “available where enabled”, for example the MCP server, Deep Research, and Tables. Ask your Default contact to turn one on.
Website Intent providers cost extra. Clearbit Reveal, Demandbase, and Vector are available at an additional cost. See Enrichment providers.
Enrichment uses credits. Default supplies the enrichment providers and counts their use in credits. See Enrichment credits in Default.
Billing and usage pages are rolling out. Billing and Usage pages in Settings are not available to every workspace yet. Your Default contact can share your current plan and credit use.

Seats and roles in Default

Seats are part of Default’s billing, and your plan sets which seats you have and their price. Each member of a workspace has 1 role:

Role	What it allows
Admin	Access to all features and actions in the workspace.
Member	Specific access to selected features and actions in the workspace.
Viewer	Read-only access. Viewers cannot be granted edit access.

An admin can invite up to 200 people in 1 send from Invite People. See Users.

Enrichment credits in Default

Default uses enrichment credits when it calls an enrichment provider, wherever the call starts: the Enrich Data workflow node, enrichment from Tables, pre-enrichment on forms and booking pages, Request enrichment in the Chrome extension, or the MCP server’s enrichment_run tool. Default supplies the provider accounts, so you don’t need an account or API key with any provider. Credits per call for person and company enrichment:

Provider	Person	Company
Clearbit	1	1
Apollo	1	1
People Data Labs	2	2
Wiza	1 to 3, by Enrichment level	1
Icypeas (email verification)	1	Does not apply
Abstract Email Reputation (email validation)	2	Does not apply

Wiza’s person cost depends on the node’s Enrichment level: None and Partial use 1 credit, Phone uses 2, and Full, the default, uses 3. Credits per call for the other credit types:

Credit type	Provider	Credits
Website visitor identification	Clearbit Reveal	1
Website visitor identification	Demandbase	2
Website visitor identification	Vector	3
IP geolocation	Abstract Geolocation	2
AI research	Parallel, used by Deep Research	1

When a call uses enrichment credits

A provider that returns data uses its credits. How many providers that is depends on where the waterfall runs. The Enrich Data node and form pre-enrichment call every provider in the waterfall at the same time, so every provider that returns data uses credits, even when a higher provider already filled its fields. Tables and the Chrome extension call providers 1 at a time and stop at the first provider that returns data, so the providers after it are not called and use nothing.
Some providers charge for every lookup. Clearbit, Clearbit Reveal, Icypeas, Abstract, and Parallel use credits even when a lookup finds no match, because the provider bills for the lookup itself.
The waterfall card shows the worst case. Each waterfall card shows the most credits 1 call can use: the sum of every provider’s cost, for when every provider is billed.
A Website Intent provider that is off uses nothing. In Enrichment providers, turning Clearbit Reveal or Demandbase off stops Default from calling it for your visitors, and turning Vector off drops its deliveries without a charge.

Public API limits in Default

Limit	Value
Rate limit	30 requests per minute per API key, shared across all endpoints and counted in fixed 1-minute windows
Over the rate limit	`429` with the code `RATE_LIMITED` and a `Retry-After` header
Date range per slots request	Up to 63 days
API key permissions	`triggers:read`, `triggers:write`, `scheduling:read`, `scheduling:write`
Where the API runs	Server to server only. It sends no CORS headers.

See Route and book through the API and Booking meetings through AI agents and the API.

Workflow and scheduling limits in Default

Limit	Value	Where
Providers per waterfall	Up to 5	Waterfalls
Guests a lead can invite to a booking	Up to 10, in Invite guests	Booking page
Additional hosts a rep can add when booking for a lead	Up to 10	Rep booking page
Redirect delay on a Display Scheduler node	0 to 300 seconds, default 10	Display Scheduler
Timeout on a Display Scheduler node	At least 3 minutes, default 5	Display Scheduler
Slack message from a workflow	4,000 characters. Default cuts longer messages off.	Notification nodes
Incoming webhook request body	Up to 1,000,000 bytes. Larger requests get `413`.	Triggers

MCP server limits in Default

The MCP server is in beta.

Limit	Value
Rows per page from `data_query`, `crm_query`, and `segment_query`	Up to 100
Date window for `available_slots`	Up to 63 days, default 7
Expiry of a link from `scheduling_link_create`	Up to 30 days, default 7
CSV file size for `upload_file`	Up to 50 MB, CSV files only

Related: Default pricing

​How plans work in Default

​Seats and roles in Default

​Enrichment credits in Default

​When a call uses enrichment credits

​Public API limits in Default

​Workflow and scheduling limits in Default

​MCP server limits in Default