Appalachian Regional Commission
The Appalachian Regional Commission (ARC) is a federal-state partnership that invests in Appalachia's economic future by funding projects that promote economic development, infrastructure improvement, workforce training, and community development across 423 counties in 13 states. ARC runs no developer program and publishes no API documentation, but it operates two live, anonymous, machine-readable surfaces: the WordPress REST API behind www.arc.gov, which serves its research reports, maps, resources, investment priorities, local development districts, events and staff as JSON; and 108 public hosted feature services in its own ArcGIS Online organization, which carry the region's boundaries and the annual county economic-status, poverty, income, SNAP, broadband, education and population series. Neither needs a key.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Appalachian Regional Commission the way a machine reads it — 24 machine-readable artifacts across 7 APIs, 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 — Appalachian Regional Commission scores 28.3/100 (thin), with a separate agent-readiness read of 40/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
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.
Put this on your own site. The badge is drawn live from Appalachian Regional Commission'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/appalachian-regional-commission/"
title="Appalachian Regional Commission on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/appalachian-regional-commission.svg"
alt="Appalachian Regional Commission Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/appalachian-regional-commission/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/appalachian-regional-commission/"
title="Appalachian Regional Commission on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/appalachian-regional-commission/card.svg"
alt="Appalachian Regional Commission 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 Appalachian Regional Commission
Each block below is one kind of artifact we hold for Appalachian Regional Commission. 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 7
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.
ARC Research and Data API
Anonymous read access to the Appalachian Regional Commission's research surface as JSON: 304 research reports, evaluations, chartbook chapters and fact sheets; 161 map records c...
ARC Geospatial API
Anonymous query access to the 108 public hosted feature services in the Appalachian Regional Commission's own ArcGIS Online organization (org id nkunl3y8FDxPkXDl, portal arcgov....
ARC Programs API
Anonymous read access to the programmatic side of ARC as JSON: the nine ARC investment priorities, the 74 Local Development Districts that deliver ARC investment across the regi...
ARC Content API
Anonymous read access to the general content surface of www.arc.gov as JSON: 204 newsroom posts, 176 site pages, a 6,293-item media library holding the PDFs behind ARC's reports...
ARC Taxonomy API
Anonymous read access to the 34 controlled vocabularies ARC classifies its content with — states_counties (446 terms), investment_priority_topic (22), tax_year (70), global_type...
ARC API Discovery
The self-describing route index for the arc.gov WordPress REST API — 371 routes across 16 namespaces, each with its HTTP methods and full argument schemas, returned as a single ...
ARC Data Report Tool
The ARC Data Report Tool provides state- and county-level data for the entire Appalachian Region across six topic areas comparing Appalachian data with national averages. Data c...
Scroll within the panel for all 7 ·
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.
Appalachian Regional Commission 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 7
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.
County-Level Data Reports
State and county-level data reports for all 423 Appalachian counties across six topic areas.
Regional Comparison Data
Appalachian Region data compared against national averages for benchmarking.
Research Reports
Regular research publications addressing socioeconomic issues in the Appalachian Region.
Maps
Geographic mapping data and visualizations covering the Appalachian Region.
Grant Program Data
Data on ARC's investment portfolios, grants, and program evaluations.
Public Feature Services
108 anonymous ArcGIS hosted feature services carrying region, county and district boundaries plus the annual economic-status and ACS statistical series.
Self-Describing Content API
A 371-route WordPress REST index exposing ARC reports, maps, resources, districts, events and staff as JSON with full argument schemas.
Scroll within the panel for all 7 ·
Security 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.
Use Cases 5
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.
Economic Research
Access county-level economic, demographic, and quality-of-life data for Appalachian research.
Grant Program Analysis
Evaluate ARC investment portfolios and grant outcomes across the Appalachian Region.
Policy Development
Use regional data to inform economic development and infrastructure policy decisions.
Community Development Planning
Access local data to support community-level economic development planning.
Distress Mapping
Join ARC county economic-status designations to other datasets on FIPS to map distressed and at-risk counties across the 13-state region.
Resources
Every other property we hold for Appalachian Regional Commission — 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 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/appalachian-regional-commission · machine-readable index on apis.io
This is an independent, third-party profile of Appalachian Regional Commission, 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.