Overview for ARP Standard
The ARP Standard is the normative, versioned HTTP+JSON contract for ARP services. It defines what endpoints exist, what payloads look like, and what “conformant” means.
ARP Standard defines the wire contract (OpenAPI + JSON Schema + conformance rules). It does not define CLIs, deployment defaults, or model-provider integrations.
For a runnable reference implementation, see JARVIS Implementation.
Who this is for
- Implementers building ARP Standard v1 services (
Run Gateway,Run Coordinator, executors, registry, selection,PDP). - Teams validating service conformance
- Client developers using generated packages (for example Python
arp-standard-client/arp_standard_client)
Spec layout (v1)
The canonical spec sources live in the ARP_Standard repository under spec/v1/:
- OpenAPI contracts:
spec/v1/openapi/*.openapi.yaml - JSON Schemas:
spec/v1/schemas/** - Examples:
spec/v1/examples/** - Conformance vectors + required endpoints:
spec/v1/conformance/** - Generated SDKs: published both to package provider services (e.g. PyPI) and to GitHub as release artifacts.
This docs section is a navigation layer over the spec. When in doubt, defer to the spec files.
- Spec v1 index:
ARP_Standard/spec/v1/README.md - Required endpoints (v1):
ARP_Standard/spec/v1/conformance/rules/required.md
Services (v1)
All services MUST implement:
GET /v1/healthGET /v1/version
ARP Standard v1 defines the node-centric execution fabric service set:
| Service | Purpose | OpenAPI | Conformance |
|---|---|---|---|
| Run Gateway | Client entrypoint for runs | run-gateway.openapi.yaml | Required endpoints are listed under Conformance. |
| Run Coordinator | Run authority + enforcement points | run-coordinator.openapi.yaml | Required endpoints are listed under Conformance. |
| Atomic Executor | Execute atomic NodeRuns | atomic-executor.openapi.yaml | Required endpoints are listed under Conformance. |
| Composite Executor | Execute composite NodeRuns | composite-executor.openapi.yaml | Required endpoints are listed under Conformance. |
| Node Registry | Catalog NodeTypes | node-registry.openapi.yaml | Required endpoints are listed under Conformance. |
| Selection | Generate bounded candidate sets | selection.openapi.yaml | Required endpoints are listed under Conformance. |
| PDP | Policy decisions (optional) | pdp.openapi.yaml | Required endpoints are listed under Conformance. |
Start here
- Service responsibilities and required endpoints: Services
- Shared payload conventions (errors, extensions, endpoint locators): Data Schemas & Conventions
- How conformance is defined and validated: Conformance
- Generated client SDKs: SDKs (Python:
arp-standard-client)
Relationship to JARVIS
JARVIS is the first-party OSS implementation of ARP. Although it is strictly compliant with ARP Standard, it may include behavior that is not required by (or not yet covered by) the ARP Standard.
See: JARVIS Implementation and the end-to-end Quickstart.