# Developer (/docs/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 [#at-a-glance]

| Goal | Start here |
| --- | --- |
| Give an agent a simple working procedure | Agent guide |
| Connect an MCP client | MCP connections |
| Find records, count, compare, or chart | MCP `execute` |
| Chain operations or make supported changes | MCP `execute` |
| Build an HTTP integration | REST API |
| Read exact inputs | `sift.spec(id)` (TypeScript) or OpenAPI (JSON Schema) |

## Read these docs as an agent [#read-these-docs-as-an-agent]

| Resource | Use it for |
| --- | --- |
| [llms.txt](https://docs.getsift.ai/llms.txt) | A short index. Start here and fetch only the relevant page. |
| [llms-full.txt](https://docs.getsift.ai/llms-full.txt) | Public docs in one text response, with developer guides first. |
| [Agent guide as Markdown](https://docs.getsift.ai/docs/developer/agent-guide.md) | Copyable agent instructions and recipes. |
| [MCP fields as Markdown](https://docs.getsift.ai/docs/developer/mcp-reference.md) | Direct tool inputs and data contracts. |
| [API fields as Markdown](https://docs.getsift.ai/docs/developer/api-reference.md) | Every declared REST field. |
| [OpenAPI JSON](https://api.getsift.ai/docs/json) | Exact 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 [#whats-in-here]

<Cards>
  <Card href="/docs/developer/agent-guide" title="Agent guide">A short working procedure, copyable instructions, and practical recipes.</Card>
  <Card href="/docs/developer/mcp-connections" title="MCP connections">Connect a client, choose authentication, and understand access controls.</Card>
  <Card href="/docs/developer/mcp" title="MCP overview">Choose a tool and understand reads, writes, and human confirmation.</Card>
  <Card href="/docs/developer/mcp-reference" title="MCP field reference">Tool inputs, search sources, analytics fields, and result contracts.</Card>
  <Card href="/docs/developer/record-fields" title="Record field dictionary">What pmid, prid, identifiers, scores, and returned row fields mean.</Card>
  <Card href="/docs/developer/api" title="REST API">Authentication, endpoints, request examples, and error handling.</Card>
  <Card href="/docs/developer/api-reference" title="API field reference">Filters, pagination, action fields, custom fields, and ingestion.</Card>
  <Card href="/docs/developer/api-keys" title="API keys">Create, use, rotate, and revoke organization keys.</Card>
  <Card href="/docs/developer/query-syntax" title="Query syntax">The filter language for Search and supported API fields.</Card>
  <Card href="/docs/developer/metrics-reference" title="Metrics reference">Definitions and calculations for analytics metrics.</Card>
</Cards>

## Who uses this [#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.

## Related [#related]

<Cards>
  <Card href="/docs/analyze" title="Dashboards and analysis">Understand the data your agent reads.</Card>
  <Card href="/docs/automate" title="Automate">Use saved searches, queues, and workflows in Sift.</Card>
</Cards>