Commission of Fine Arts
The U.S. Commission of Fine Arts (CFA) is an independent federal agency established in 1910 that has review authority over the design and aesthetics of construction within Washington, D.C., and over coins, medals, and Federal commemorative works. The CFA also appoints the Old Georgetown Board which conducts design review for projects in the Georgetown Historic District. As of September 2026 the CFA publishes no public developer API, no OpenAPI specification and no developer program. Its roughly 19,500 project records are reachable only through a server-rendered Drupal Search API view at cfa.gov/records-research/project-search and through the records-and-research request process. The only machine-readable surfaces the agency serves are a sitemap.xml, a robots.txt and three RSS 2.0 feeds (blog, news, meetings). The CFA does publish a CISA-aligned Vulnerability Disclosure Policy with a security@cfa.gov contact and stated 3/7/90-day response targets.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Commission of Fine Arts the way a machine reads it — 4 machine-readable artifacts, 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 — Commission of Fine Arts scores 10.1/100 (minimal), with a separate agent-readiness read of 3/100 (human only). 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 CFA runs one Drupal 10 site whose ~19,500 project records are served only as HTML through a Search API view — /jsonapi, /api, /openapi.json, /data.json and /llms.txt all 404, no api./data./developer. subdomain resolves in DNS, and the agency has no developer portal, SDK or webhook surface of any kind.
This is an honest zero, not a gap in our research. Commission of Fine Arts 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.cfa.gov/jsonapi→ HTTP 404https://www.cfa.gov/openapi.json→ HTTP 404https://www.cfa.gov/developer→ HTTP 404https://www.cfa.gov/.well-known/api-catalog→ HTTP 404https://www.cfa.gov/records-research/project-search→ HTTP 200
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-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Commission of Fine Arts'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/commission-of-fine-arts/"
title="Commission of Fine Arts on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/commission-of-fine-arts.svg"
alt="Commission of Fine Arts Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/commission-of-fine-arts/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/commission-of-fine-arts/"
title="Commission of Fine Arts on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/commission-of-fine-arts/card.svg"
alt="Commission of Fine Arts 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 Commission of Fine Arts
Each block below is one kind of artifact we hold for Commission of Fine Arts. 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.
Pricing 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.
Commission Of Fine Arts Rate Limits
RATE LIMITSSecurity Posture 2
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.
Resources
Every other property we hold for Commission of Fine Arts — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/commission-of-fine-arts · machine-readable index on apis.io
This is an independent, third-party profile of Commission of Fine Arts, 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.