Architect of the Capitol
The Architect of the Capitol (AOC) serves Congress and the Supreme Court as builder and steward of Capitol Hill's landmark buildings and grounds, preserving historic structures, monuments, art, and gardens across the Capitol campus.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Architect of the Capitol the way a machine reads it — 56 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Architect of the Capitol scores 47.2/100 (developing), with a separate agent-readiness read of 20/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
The Architect of the Capitol is a legislative-branch construction and preservation agency with no developer program at all — www.aoc.gov/developers and /api both return 404, there is no pricing, portal or reference page anywhere in its 1,092-URL sitemap, and api.aoc.gov (the host named in the scaffolded OpenAPIs this repo holds) does not resolve in DNS.
This is an honest zero, not a gap in our research. Architect of the Capitol does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://www.aoc.gov/developers→ HTTP 404https://www.aoc.gov/api→ HTTP 404https://www.aoc.gov/.well-known/api-catalog→ HTTP 404https://www.aoc.gov/llms.txt→ HTTP 404https://api.aoc.gov/openapi.json→ HTTP 0
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Architect of the Capitol's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/architect-of-the-capitol/"
title="Architect of the Capitol on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/architect-of-the-capitol.svg"
alt="Architect of the Capitol Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/architect-of-the-capitol/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/architect-of-the-capitol/"
title="Architect of the Capitol on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/architect-of-the-capitol/card.svg"
alt="Architect of the Capitol Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Architect of the Capitol
Each block below is one kind of artifact we hold for Architect of the Capitol. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Architect of the Capitol Accessibility API
The Accessibility API from Architect of the Capitol — 1 operation(s) for accessibility.
Architect of the Capitol Art Collection API
The Art Collection API from Architect of the Capitol — 2 operation(s) for art collection.
Architect of the Capitol Buildings API
The Buildings API from Architect of the Capitol — 2 operation(s) for buildings.
Architect of the Capitol Preservation API
The Preservation API from Architect of the Capitol — 2 operation(s) for preservation.
Architect of the Capitol Visitor Information API
The Visitor Information API from Architect of the Capitol — 1 operation(s) for visitor information.
Open Collections 6
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONArchitect of the Capitol Data Accessibility API
OPEN COLLECTIONArchitect of the Capitol Data Accessibility Buildings API
OPEN COLLECTIONArchitect of the Capitol Data Accessibility Preservation API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Architect Of The Capitol Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Features 5
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Capitol Campus Buildings
Information about the US Capitol, House and Senate office buildings, Library of Congress, and Supreme Court.
Art Collections
Access to the Capitol art collection catalog including paintings, sculptures, and historic artifacts.
Historic Preservation Projects
Data on preservation and restoration projects across the Capitol campus.
Accessibility Information
Accessibility features and visitor accommodations across Capitol campus facilities.
Congressional Facilities
Management of congressional office space, hearing rooms, and support facilities.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Aoc Data Api Context
JSON-LDSpectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Architect of the Capitol API Rules
SPECTRALArchitect of the Capitol API Rules
SPECTRALArchitect of the Capitol API Rules
SPECTRALJSON Schema 9
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccessibilityInfo
JSON SCHEMAArtworkList
JSON SCHEMAArtwork
JSON SCHEMABuildingList
JSON SCHEMABuilding
JSON SCHEMACoordinates
JSON SCHEMAPreservationProjectList
JSON SCHEMAPreservationProject
JSON SCHEMAVisitorInfo
JSON SCHEMAScroll within the panel for all 9 ·
JSON Structure 9
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Aoc Data Api Accessibility Info Structure
JSON STRUCTUREAoc Data Api Artwork List Structure
JSON STRUCTUREAoc Data Api Artwork Structure
JSON STRUCTUREAoc Data Api Building List Structure
JSON STRUCTUREAoc Data Api Building Structure
JSON STRUCTUREAoc Data Api Coordinates Structure
JSON STRUCTUREAoc Data Api Preservation Project List Structure
JSON STRUCTUREAoc Data Api Preservation Project Structure
JSON STRUCTUREAoc Data Api Visitor Info Structure
JSON STRUCTUREScroll within the panel for all 9 ·
Examples 9
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Aoc Data Api Artwork Example
EXAMPLEScroll within the panel for all 9 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Visitor Information
Provide Capitol campus visitor information including building access, tours, and facilities.
Art Research
Research the Capitol art collection for educational and historical purposes.
Historic Preservation
Track preservation project status and outcomes for historic Capitol structures.
Congressional Services
Support congressional staff with facilities management and space planning information.
Resources
Every other property we hold for Architect of the Capitol — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/architect-of-the-capitol · machine-readable index on apis.io
This is an independent, third-party profile of Architect of the Capitol, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.