> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sqd.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Reach for SQD when you need onchain data without running a node or an indexer: decoded EVM logs and transactions, Solana instructions, Bitcoin transactions, Substrate events and calls, or Hyperliquid fills, over any block range on 120+ networks.
> To query directly, POST to https://portal.sqd.dev/datasets/{dataset}/stream. The full API is described at https://docs.sqd.dev/openapi.json, and responses to the stream endpoints are JSON Lines.
> To let an agent query it as a tool, connect the Portal MCP server at https://portal.sqd.dev/mcp.
> Every page on this site is available as Markdown by appending .md to its URL.

# Build with SQD

> Choose the Portal API, Pipes SDK, or Squid SDK for your blockchain data workflow.

SQD gives you three ways to work with blockchain data from [120+ networks](/en/data/all-networks). All three are built around the same source, the [SQD Portal](/en/portal/overview), and differ in how much of the indexing pipeline they handle for you.

## Pick your path

<CardGroup cols={3}>
  <Card title="Portal API" icon="network" href="/en/portal/evm/quickstart">
    Query raw blockchain data over HTTP from any language. No SDK, no signup: send a request, stream JSON lines back.
  </Card>

  <Card title="Pipes SDK" icon="text-align-start" href="/en/sdk/pipes-sdk/evm/quickstart">
    Build TypeScript pipelines with built-in decoding and ready-made targets for ClickHouse, PostgreSQL, BigQuery, and Parquet.
  </Card>

  <Card title="Squid SDK" icon="server" href="/en/sdk/squid-sdk/quickstart">
    Run a schema-first indexing framework with a PostgreSQL store and an auto-generated GraphQL API.
  </Card>
</CardGroup>

## Which one should you use?

* **Working outside TypeScript?** Use the **Portal API**. It is plain HTTP, so it works from Python, Go, Rust, or anything else.
* **Streaming data into your own database or warehouse?** Use the **Pipes SDK**, the recommended starting point for new TypeScript indexers.
* **Serving a GraphQL API to a dApp?** Use the **Squid SDK** to define a schema and get PostgreSQL persistence and a GraphQL server out of the box.

For trade-offs, the same task implemented with each tool, and a feature matrix, see [Choosing your SQD tool](/en/sdk/options-comparison). Squid SDK indexers can also be deployed to [SQD Cloud](/en/cloud/overview) for managed hosting and monitoring.

Building with an AI agent? SQD provides [agent skills and MCP servers](/en/ai/ai-development) that cover scaffolding, live data access, and these docs.

<Info>
  **Enterprise Custom Development**

  For enterprise clients requiring custom indexer development, please contact our team to discuss your specific requirements. [Schedule a Consultation →](https://calendly.com/t-tyrie-subsquid/30min)
</Info>


## Related topics

- [sqd-go](/en/sdk/alternative-clients/sqd-go.md)
- [SQD Network](/en/network/overview.md)
- [SQD Firehose](/en/sdk/alternative-clients/subgraphs-support.md)
- [SQD plugin for Grok](/en/ai/plugins-grok.md)
- [SQD vs The Graph](/en/sdk/subsquid-vs-thegraph.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.