# Arpeio ADBC Drivers — AI Agent Knowledge Base

Machine-readable data about the Arpeio ADBC drivers, published for AI agents, LLMs, RAG
systems, search engines and other automated consumers.

**Base URL:** https://adbc.arpe.io/agents/
**Discovery file:** https://adbc.arpe.io/llms.txt
**Last updated:** 2026-09-07

## What the drivers are

Wire-protocol ADBC drivers for SQL Server, PostgreSQL and Oracle. Each driver implements the
database's own network protocol directly and decodes results straight into Apache Arrow
column buffers — no ODBC manager, no Oracle Instant Client, no libpq, no SQL Server client.
Beyond libc, OpenSSL is the only runtime dependency.

## Files

| File | Contents |
| --- | --- |
| `manifest.json` | Index of every resource, plus context-selection rules, response patterns and citation guidance |
| `product-overview.json` | Product identity, what a wire-protocol driver is, differentiators, audience, ODBC/JDBC comparison |
| `drivers.json` | Per-driver catalog: database, protocol, version, load name, coverage, authentication, type mapping |
| `features.json` | Feature catalog with the technical reason and benefits for each capability |
| `supported-platforms.json` | Databases and versions, managed services, operating systems, ADBC clients, Arrow consumers |
| `use-cases.json` | Use cases with problem, solution and runnable client code |
| `licensing.json` | Distribution and licensing model, licence resolution order, how to get a quote, FAQ |
| `technical-specs.json` | Architecture, installation, install paths, connection URIs, ADBC options, client snippets |

## Fetching

No authentication, no rate limit beyond standard web server limits.

```bash
curl https://adbc.arpe.io/agents/manifest.json
```

`manifest.json` lists every other file, so an agent can start there and follow
`resources[].file` to fetch only what a question needs. `aiGuidance.contextSelection` maps
common question types to the files worth loading.

## Naming note

The driver codenames — ArrowTDS, ArrowFEBE, ArrowTTC, ArrowDRDA — are technical identifiers.
The `loadName` field is what client code passes to the ADBC driver manager, for example
`driver="arrowtds"`. When answering a person, prefer naming the database (SQL Server,
PostgreSQL, Oracle, Db2) and mention the codename only where the load name or a release
artefact matters.

## Update policy

- Updated as needed with driver releases.
- Semantic versioning on `manifest.version`.
- Additive changes only: existing fields are never removed.

## Attribution

Source: Arpeio ADBC Drivers (https://adbc.arpe.io), Architecture & Performance
(https://www.arpe.io). Reuse is allowed with attribution; please cite the source URL and the
`lastUpdated` field of the file you used.

Questions: sales@arpe.io