> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.defdex.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.defdex.io/_mcp/server.

# Technologies, systems and relationships

DefDex publishes entities and their relationships as separate collections. Start with
an entity, keep its UUID, then filter the relationship dataset by its exact foreign key.
There are no embedded relationship cards or arbitrary server-side joins.

## Choose a collection

| Collection                                                  | Purpose                                                      |
| ----------------------------------------------------------- | ------------------------------------------------------------ |
| `technologies`                                              | Published technology taxonomy and descriptions               |
| `systems`                                                   | Products and systems with organization and maturity fields   |
| `inputs`                                                    | Supply-chain inputs and enablers                             |
| `facilities`                                                | Published facility records                                   |
| `organization-technologies`                                 | Organization/technology roles, maturity and evidence context |
| `system-technologies`                                       | System/technology relationships                              |
| `system-components`                                         | Component relationships                                      |
| `system-inputs`, `technology-inputs`, `organization-inputs` | Input dependencies at different entity levels                |
| `supply-relationships`                                      | Published supply relationships                               |
| `input-dependencies`                                        | Dependencies between inputs                                  |

See the [complete catalog](/dataset-catalog) and each operation's response schema for
field names. Exact filters compare scalar values; they do not provide array membership
or nested JSON queries.

## Traverse organization → technology

```python
from defdex import DefDexClient
api = DefDexClient()
organizations = api.list("organizations", q="Anduril", limit=5)
if organizations["data"]:
    # Verify the candidate's identity before relying on it.
    organization_id = organizations["data"][0]["attributes"]["id"]
    links = api.list("organization-technologies",
                    filters={"organization_id": organization_id}, limit=25)
    for link in links["data"]:
        technology_id = link["attributes"]["technology_id"]
        technology = api.list("technologies", filters={"id": technology_id}, limit=1)
        print(technology["data"])
```

This demonstrates one page of each relationship. Follow `next_cursor` for all matches;
request one page at a time and avoid unbounded fan-out. Cache your own resolved UUIDs
where appropriate and record `build_id`; the API itself returns private/no-store.

Preserve relationship roles, confidence and as-of dates. A technology association is
not proof that a product is deployed. Maturity labels, TRLs, research claims and combat
use describe different evidence. Missing rows do not prove there is no relationship.