SiftDocs
Developer

Developer

Connect an agent to Sift, or build an integration with the REST API. Start with the agent guide, then use the field references for exact requests.

At a glance

GoalStart here
Give an agent a simple working procedureAgent guide
Connect an MCP clientMCP connections
Find records, count, compare, or chartMCP execute
Chain operations or make supported changesMCP execute
Build an HTTP integrationREST API
Read exact inputssift.spec(id) (TypeScript) or OpenAPI (JSON Schema)

Read these docs as an agent

ResourceUse it for
llms.txtA short index. Start here and fetch only the relevant page.
llms-full.txtPublic docs in one text response, with developer guides first.
Agent guide as MarkdownCopyable agent instructions and recipes.
MCP fields as MarkdownDirect tool inputs and data contracts.
API fields as MarkdownEvery declared REST field.
OpenAPI JSONExact REST request and response schemas.

Use the index plus focused pages for most tasks. Use the full text when the client needs one document. For MCP operations, read the current declaration with sift.spec(id) instead of assuming a static reference never changes.

What's in here

Who uses this

Agent builders use MCP for discovery and permission-checked operations. Integration developers use the REST API for explicit HTTP requests.

Both connections stay within their authenticated organization. MCP tool availability also depends on the person's access and enabled features.

On this page