Data & Bases

A base is an org-level data container — the system of record behind your hubs. These pages are generated from the WayAI skill, the CLI, and the MCP server itself, so they never drift from what ships.

• Bases — the Data surfaceOpen this the moment a task involves a base: designing a schema, reading or writing records, linking entities, storing files, wiring an integration, or building an agent-facing toolset. It is the complete concept map for the Data surface; the sibling files carry the field-level grammar.
• Record types, records, relationshipsOpen this before authoring a record-type schema, writing or querying records, linking entities, or loading data in bulk. Concepts are in Bases — the Data surface; this is the command and schema grammar.
• Querying & searchDeep how-to for reading a base: the wayai bases sql surface and its mandatory scoping, a worked SQL example gallery, search-field tuning (x-search), and datetime/timezone configuration. Open it when a read needs more than a single filter, when approximate matching returns the wrong things, or when datetimes come back in an unexpected zone. The entity model, the Filter DSL operators, and the day-to-day command shapes live in SKILL.md in the WayAI skill and Record types, records, relationships.
• Files and attachmentsOpen this before storing PDFs, images, generated reports, or any large/binary content in a base. Concepts are in Bases — the Data surface.
• Base config as code, environments, and seed fixturesOpen this when managing a base's config in git, moving config between preview and production, or setting up hermetic data for agent evals. Concepts are in Bases — the Data surface.
• IntegrationsHow a base reaches an external system: external sources (back a record_type with an upstream API), inbound webhooks (data in), triggers (data out), and provider adapters. Open this when you are backing a record_type with something outside the base, or wiring change notifications in either direction — and read Canonical-first modeling before picking an edge.
• Toolsets and Actions (the MCP factory)How a base publishes a purpose-built MCP server for an agent: Actions (the tool definitions), toolsets (the surface that composes them), the tokens that reach them, and the credentials behind them. Open this when you are about to author or debug a curated tool surface over base data — for the base ontology itself see Record types, records, relationships and Querying & search; for the config-as-code round trip see Base config as code, environments, and seed fixtures.
• ExecutorsWhat an executor is, whether you need one, and the contract it must honor. Open this when a trigger or an external source has to act on the outside world — call a third-party API, present a client certificate, run logic the Data backend can't run itself.
• CLI command referenceEvery command the wayai CLI exposes for working with bases, walked directly from the command tree the binary ships. Options shown on a namespace are honored by every command beneath it.
• MCP tool referenceEvery tool the Data MCP server registers, read from the server's own registration list so this page cannot describe a tool an agent is not actually served. These are the platform tools — generic operations over bases, record types, records, relationships, files and triggers.

Working with an AI coding agent? Install the WayAI skill and it loads these references on demand. See Get Started.