Adapter catalog
Every adapter built into the gtme binary with its role, record type, needs, provides, cost, and credentials, generated from its manifest
What you'll learn
You need an adapter for a step and want to see every built-in at once, with what each needs, writes, and costs.
- every built-in adapter by role
- what each needs, provides, and costs
- which steps the runner owns without an adapter
The 15 adapters built into the gtme binary, by role. Each row links the adapter's own page: its manifest, every with: key it accepts, and an example step. gtme help --agent prints the same manifests as JSON, and gtme adapters lists what's installed beside them, which the registry can add to.
| Adapter | Role | Records | Needs | Provides | Per record | Credentials |
|---|---|---|---|---|---|---|
csv/source | source | person | nothing | none declared | not published | none |
demo/enrich | enrich | person | any of email or full_name | 2 | $0.0100 | none |
http/enrich | enrich | person | the step's uses: fields | none declared | not published | none |
agent/filter | filter | any type | the step's uses: fields | none declared | not published | none |
ai/filter | filter | any type | the step's uses: fields | none declared | not published | ANTHROPIC_API_KEY (optional), ANTHROPIC_WORKSPACE_ID (optional) |
human/filter | filter | any type | the step's uses: fields | none declared | not published | none |
agent/compose | compose | any type | the step's uses: fields | 2 | not published | none |
ai/compose | compose | any type | the step's uses: fields | 2 | not published | ANTHROPIC_API_KEY (optional), ANTHROPIC_WORKSPACE_ID (optional) |
human/compose | compose | any type | the step's uses: fields | 2 | not published | none |
text/compose | compose | any type | the step's uses: fields | none declared | not published | none |
agent/review | review | any type | the step's uses: fields | none declared | not published | none |
ai/review | review | any type | the step's uses: fields | none declared | not published | ANTHROPIC_API_KEY (optional), ANTHROPIC_WORKSPACE_ID (optional) |
human/review | review | any type | the step's uses: fields | none declared | not published | none |
csv/deliver | deliver | person | the step's uses: fields | none declared | $0 | none |
http/deliver | deliver | person | the step's uses: fields | none declared | not published | none |
Needs is what a record must already carry for the adapter to run; the step's uses: fields means the step declares them. Provides counts the fields it can write. Per record is the estimate plan prints, and not published prints as ? there.
Runner-owned steps
These have no manifest and no adapter session; the runner executes them from a query: in with:.
| Step | Does |
|---|---|
use: sql/filter — with: {query: "SELECT identity_id, pass[, reason] FROM ..."} | runner-owned filter: rows decide pass/fail per eligible record (a missing row, or pass=0, fails it with the reason recorded); read-only against the §3 surface, $0 |
use: sql/transform — with: {query: "SELECT identity_id, <expr> AS \"ns.field\" ..."} | runner-owned derivation: result columns append like adapter output (registry-checked, provenance sql/transform @ \<query-hash\>); declare provides: [ns.field]; cross-record aggregates and fan-in live here |
use: sql/traverse — with: {entity_type: <type>, query: "SELECT r.to_id AS identity_id, r.from_id AS parent_id FROM relations r WHERE r.relation = 'works_at'"} | runner-owned traverse (ADR-054): follows relations the ledger already holds — the companies of this run's people — into a new leg of entity_type; mints nothing, writes no relation; parents are finished here, only the children continue |
Used in
- A pipeline is a YAML file
- Steps and roles: Every shipped adapter with its role, needs, and provides
- Canonical fields: Each shipped adapter's provides, canonical and namespaced
- Two adapter tiers: Every adapter the binary ships, with its role and kind