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

# Introduction

> Verified intelligence on the AI race. Built for agents.

<Note>
  Building an agent? Load the entire docs as one file from [`/llms-full.txt`](https://docs.gildea.ai/llms-full.txt).
</Note>

Gildea is the market data API for AI. We transform raw events and expert analysis on the AI economy into atomic intelligence your agent can query. We do this by sourcing, structuring, and verifying signals from 500+ leading sources worldwide. Gildea data is served through a REST API and an MCP server, with new signals added daily.

## Make your first call

Base URL `https://api.gildea.ai/v1`, authenticated with an `X-API-Key` header. One request returns verified, source-cited claims:

```bash theme={null}
curl -H "X-API-Key: $GILDEA_API_KEY" \
  "https://api.gildea.ai/v1/search?q=AI%20chip%20export%20controls&role=claim&limit=5"
```

## What you get

<CardGroup cols={2}>
  <Card title="Source Curation" icon="filter" href="/concepts/signals">
    Built for agents that need to know what experts know, not what the web indexes. Gildea curates 500+ of the highest-signal AI sources that crawlers miss or bury in SEO sludge. Each is hand-picked by people who track AI for a living.
  </Card>

  <Card title="Signal Distillation" icon="compress" href="/concepts/signals">
    Built for agents that need to reason, not just retrieve. A model's reasoning degrades as its context fills with noise, so Gildea distills each source to its strategic spine, giving your agent dense, relevant input instead of bloat.
  </Card>

  <Card title="Signal Enrichment" icon="sitemap" href="/concepts/entities">
    Built for agents that need to filter, route, and connect, not just read. Every signal is classified by content type, tagged to themes, and linked to the entities it names with stable IDs, so your agent can scope, pivot, and trace relationships instead of parsing prose.
  </Card>

  <Card title="Signal Verification" icon="shield-check" href="/concepts/verification">
    Built for the teams where a hallucinated claim blows up the deck, the deal, or the trade. Every sentence is scored against verbatim evidence and run through safety checks for fabricated entities, numbers, and dates. Only evidence-backed sentences are served.
  </Card>
</CardGroup>

## Built for

Gildea is purpose-built for enabling continuous monitoring use cases. Keep your view current as the AI landscape evolves:

* Create a context layer that compounds with every new signal
* Pressure-test a thesis against value-chain and market-force shifts
* Track how expert consensus shifts on a contested question
* Build category authority with fully cited content

## Design principles

* **Fresh daily.** New signals are sourced, verified, and indexed every day.
* **Verified by default.** Only evidence-cited content is ever served, so there is no unverified text to filter.
* **Structured and typed.** One unit shape across search and detail, with consistent field names and typed enums.
* **Stable identifiers.** Entities resolve to opaque `gld:/` IDs that stay constant as the corpus grows.
* **Machine-first.** Built for programmatic use: cursor pagination, `window` shortcuts, an OpenAPI spec, and `llms-full.txt`.

## Data model

A signal is an expert analysis or an event report. Gildea decomposes each into verified units: a central thesis or synopsis, the supporting argument sentences, and atomic claims, each tied to verbatim evidence from its source. Every unit is tagged to the entities it names (companies, people, and models, with stable `gld:/` IDs) and to themes (the AI value chain and market forces), so an agent can search, scope, and trace relationships across the whole corpus.

## Next steps

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">First request in 5 minutes</Card>
  <Card title="Recipes" icon="route" href="/guides/recipes">Build a verified view step by step, from question to cited answer</Card>
  <Card title="API reference" icon="code" href="/api-reference/signals/list">Every endpoint</Card>
  <Card title="MCP server" icon="robot" href="/guides/mcp">Use Gildea in Claude & more</Card>
</CardGroup>