Application Identity & Verification › Consent & Preferences

Consent & Preferences

AE-160.50 Level 2 API Evangelist extension API Evangelist extension, CC BY-NC-SA 42 providers 62 API surfaces 28 rated strong or better

Recording what a user agreed to.

Consent & Preferences (AE-160.50) is a level-2 business capability under Application Identity & Verification in the API Evangelist extension model. The catalog holds 62 API surface(s) from 42 provider(s) that can perform some part of it, 28 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of the API Evangelist extension to the business-capability model, written by API Evangelist and licensed CC BY-NC-SA 4.0. API Evangelist capability extension — https://apievangelist.com Audience: consumerb2b It extends, and never modifies, Turbo EA Capabilities by Vincent Verdet (CC BY 4.0). · Extension provenance and licence

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 14 Complete, well-documented, and agent-ready
Strong 14 Solid coverage with minor gaps
Developing 14 Usable, with meaningful gaps to close
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Consent & Preferences. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →