The Federal Protective Service uses its security expertise and law enforcement authority to protect federal government facilities and safeguard the millions of employees and visitors who pass through them every day.
Federal Protective Service is profiled on the APIs.io network. Tagged areas include Federal Government, Security, Law Enforcement, Public Safety, and Physical Security.
Federal Protective Service’s developer surface includes engineering blog and 3 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Government & Public Sector regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/federal-protective-service/"><img src="https://apis.io/badge/federal-protective-service/card.svg" alt="Federal Protective Service on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Machine-Readable Auth+10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
13 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
aid: federal-protective-service
name: Federal Protective Service
description: The Federal Protective Service uses its security expertise and law enforcement authority to protect federal government
facilities and safeguard the millions of employees and visitors who pass through them every day.
type: Index
deliveryModel:
model: unknown
open_source: false
commercial: false
callable_host: false
label: Delivery model not determined — needs a product licence on record
confidence: low
source:
- none
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
probe_state: none
source:
- security
generated: '2026-11-06'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/federal-protective-service.png
access: 3rd-Party
created: '2024-12-03'
modified: '2026-10-06'
position: Consuming
tags:
- Federal Government
- Security
- Law Enforcement
- Public Safety
- Physical Security
- Homeland Security
tags_raw:
- Federal Government
- Security
- Law Enforcement
- Public Safety
- Physical Security
- Homeland Security
- Federal-Government
url: https://raw.githubusercontent.com/api-evangelist/federal-protective-service/refs/heads/main/apis.yml
specificationVersion: '0.23'
apis: []
common:
- url: https://www.dhs.gov/news
type: Blog
- type: DomainSecurity
url: security/federal-protective-service-domain-security.yml
- type: LinkedIn
url: https://www.linkedin.com/company/fpsdhs
- type: Website
url: https://www.dhs.gov/federal-protective-service
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
x-enrichment:
date: '2026-09-09'
status: minimal
artifacts_added: 1
pass: local-v3
x-coverage:
state: none
reason: no-developer-program
detail: The Federal Protective Service publishes no host of its own (fps.dhs.gov does not resolve) and is absent from the
Department of Homeland Security developer program at https://www.dhs.gov/developer, which lists only NTAS, MyTSA and FEMA
APIs; the GSA federal API inventory carries no FPS row and the DHS Project Open Data catalog (1,168 datasets) has no FPS-published
dataset or API distribution.
evidence:
- url: https://www.dhs.gov/developer
status: 200
- url: https://www.dhs.gov/data.json
status: 200
- url: https://www.dhs.gov/.well-known/api-catalog
status: 404
- url: https://www.dhs.gov/openapi.json
status: 404
- url: https://raw.githubusercontent.com/GSA/federal-apis/master/inventory/federal-API-list.csv
status: 200
checked: '2026-09-09'
x-parent: department-of-homeland-security
x-relationship: division
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.