# Device Info

Source-linked operating-system, kernel, browser, and Apple hardware intelligence covering release chronology, build and installability variants, observed lifecycle state, hardware identifier resolution, evidence-based compatibility, and best-effort request discovery.

## Access

- Kind: api
- Audience: public
- Access: open
- Authentication: No authentication is required for documented public read operations; agent state, proposal review, pipeline mutation, and import routes are private and gated by an administrative key.
- Lifecycle: active
- Observed health: operational

## Integration links

- Base URL: https://deviceinfo.datasourceapi.com
- Documentation: https://deviceinfo.datasourceapi.com/docs/
- OpenAPI: https://deviceinfo.datasourceapi.com/openapi.yaml
- Status: https://deviceinfo.datasourceapi.com/api/v1/status
- Repository: https://github.com/coopalliance/cca-deviceinfo
- Catalog metadata: https://services.datasourceapi.com/api/v1/services/deviceinfo

## Capabilities

- apple-hardware-models
- browser-release-history
- device-discovery
- hardware-identifier-resolution
- os-lifecycle
- os-release-history
- release-compatibility
- software-release-history

## Provenance and freshness

- CCA Device Info repository contract: Routes, Wrangler configuration, custom domain, OpenAPI 3.1 document, service-binding contract, and agentic update policy verified at repository commit bd6950b71463ad4cd59bc873baf3182b1eab4ec7. (https://github.com/coopalliance/cca-deviceinfo/tree/bd6950b71463ad4cd59bc873baf3182b1eab4ec7)
- Live catalog and automation status: Public status verified 2026-09-08 reports 7 platforms, 82 operating-system releases, 135 hardware models, 33 software products, 58,788 software releases, 115,050 append-only release observations, 29 browser products, 11 configured automation sources with all healthy, a successful scheduled run, and 143 proposals pending review. (https://deviceinfo.datasourceapi.com/api/v1/status)
- Upstream source registry: The public source registry lists 64 upstream sources with per-source authority and last-success timestamps, including Apple developer, security, and model-identification pages, Chromium Dash, Mozilla, Microsoft lifecycle exports, and app-store listings. (https://deviceinfo.datasourceapi.com/api/v1/sources)
- Documented source boundaries: Records source-by-source scope, retention, attribution, and the explicit limits of vendor-derived lifecycle and hardware data. (https://github.com/coopalliance/cca-deviceinfo/blob/bd6950b71463ad4cd59bc873baf3182b1eab4ec7/docs/DATA_SOURCES.md)

Update cadence: A daily Cloudflare cron ensures the durable updater agent exists and the agent owns an idempotent six-hour refresh schedule; GitHub Actions run daily incremental and weekly full software-history reconciliation. The latest recorded agent run completed 2026-09-08 after checking 3 due sources, applying 76 of 86 proposals.. Metadata last verified: 2026-09-08.

Governance: Discovery, user-agent, client-hint, and first-party fingerprint results are unverified and spoofable parsing output. They are never device attestation and must not be used as authentication, authorization, enrollment, management, or integrity evidence. Coverage is source-observed rather than complete: a supported state means a relevant vendor release was observed, not that every known vulnerability is fixed, and products without a public vendor history are never presented as complete. Facts proposed from semi-structured vendor pages by Workers AI are applied only after deterministic schema, date, identifier, and provenance validation, and community claims stay pending review. The service does not yet publish llms.txt or an RFC 9727 catalog, and its OpenAPI document omits operationId, so the operations recorded here are catalog-curated identifiers for verified public routes. Automated parsing and redistribution of vendor support pages may be restricted by site terms; the repository documents source boundaries and states that commercial deployment needs legal review.


## Agent readiness

partial (70/100): A live OpenAPI 3.1 document, hosted documentation, a fleet response envelope, a published service-binding contract, and 16 verified public read operations exist. The document omits operationId, and llms.txt and RFC 9727 discovery are not published, so agents must treat the recorded operation identifiers as catalog-curated and discovery-assisted rather than upstream-authoritative.

## Examples

### Service status

Inspect catalog coverage, source health, and the latest updater-agent run.

```http
GET https://deviceinfo.datasourceapi.com/api/v1/status
```

### Current macOS releases

List the macOS releases currently observed as current patch trains.

```http
GET https://deviceinfo.datasourceapi.com/api/v1/os/releases?platform=macos&current=true
```

### Resolve a hardware identifier

Resolve the Macmini9,1 hardware identifier to its marketing model and aliases.

```http
GET https://deviceinfo.datasourceapi.com/api/v1/hardware/models/Macmini9,1
```

### Compatibility evidence

Check a macOS major version against one Apple hardware identifier and return null instead of guessing when authoritative evidence is missing.

```http
GET https://deviceinfo.datasourceapi.com/api/v1/compatibility?model=Macmini9,1&platform=macos&version=26
```

### Browser release history

Read the newest recorded Firefox release from the generalized browser history.

```http
GET https://deviceinfo.datasourceapi.com/api/v1/browser/releases?product=firefox&limit=1
```