Terms

Licence and bulk use

What you may do with the RPF catalogue, what anonymous access allows, and how to ask for more.

The licence

Catalogue content — roles, competency profiles, information uses, flows, action statements and the relationships between them — is licensed under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC-BY-NC-SA-4.0).

In plain terms: quote it, cite it, build on it, and pass it on — with attribution, under the same licence, for non-commercial purposes. Commercial use, including training a commercial model on bulk extracts, needs permission. Asking is usually enough; this is a standards project and distribution is the point.

What anonymous access gives you

Canonical pages stay fully public and indexable.
Nothing here is behind a wall, and named AI crawlers are welcome.
Slug-level detail returns complete records.
One role, one profile, one flow — everything, so citation and single-item use are unaffected.
List endpoints are paginated and summarised.
They return a teaser (title, summary, slug, type) rather than full rows. This removes the bulk shortcut, not the reading surface.
Reads are metered per identity per day
Counted in rows served rather than requests — so the response format makes no difference to what a read costs. Every response tells you what is left, in ratelimit-remaining-rows.

If you need more

The allowance is set well above ordinary reading and well below a systematic re-harvest. If your work needs more than that, it is a conversation rather than an obstacle — research, public-good and partner integrations are the reason this catalogue exists.

Get in touch and tell us what you are building.

The API

The spec is published at /api/openapi.json (OpenAPI 3.1), and machine-readable terms at /llms.txt.

Version 1.0.0 is stable. Send Accept: application/vnd.rpf.v1+json to pin the major version. Documented response shapes will not change incompatibly within v1. New properties may appear on any response, so ignore ones you do not recognise. See the developer guide for the full deprecation policy.

Where to go next