Select Language

Get Your Transparency Score

Connect your AI governance audit log to C.R.E.E.D. and earn a continuously-computed, publicly-verifiable transparency score — and an embeddable badge to prove it.

Apply to Connect Read the Schema Spec

Free — ≤50,000 events/day  ·  Free forever for nonprofits  ·  No vendor lock-in

FOUR STEPS

01
Apply
Contact the Institute with your organization name, website, and a brief description of your AI systems (what they do, who uses them). We verify real-org identity before creating any public listing — no anonymous tenants.
02
Tenant & Key
Once approved, we create your tenant and issue a scoped ingest key (creed_sk_…). You manage your keys from the org-admin portal at creed.kytranempowerment.com/tenant/. Keys are scoped to ingest only; public reads require no key at all.
03
Connect Your Feed
Install the Python client (zero dependencies) and start emitting events. Any platform can POST directly to the REST API — the schema is an open standard, not a library.
# install pip install "creed-client @ git+https://github.com/KytranKatarn/kytran-creed.git#subdirectory=clients/python" # connect from creed_client import CreedClient creed = CreedClient( base_url="https://api.creed-ai.org", api_key="creed_sk_...", # your tenant ingest key ) # emit an event — systems, never data subjects creed.emit_event( event_type="welfare_rest", source_platform="acme-orchestrator", agent_id="worker-7", category="fairness", # transparency|fairness|safety|privacy|accountability severity="info", # info|warning|violation|critical description="agent rested after reaching daily token budget", )
Or POST directly: POST https://api.creed-ai.org/api/v1/events with Authorization: Bearer creed_sk_…. Full schema: standard.html.
04
Score Goes Live
After your feed reaches ≥100 events across ≥3 pillars spanning ≥14 days, your score is published — a per-pillar breakdown, an overall grade (A+…F), freshness display, and embeddable SVG badges. Until then your badge reads PROVISIONAL — three info events cannot buy an A+. Every profile also shows feed freshness, so silence is visible rather than flattering.

YOUR BADGE

Once scored, you get an embeddable SVG badge for your README, website, or app. Badges carry a verification tier label: SELF-REPORTED (default), SIGNED (HMAC-attested events), or AUDITED (third-party attested). A self-reported A+ visibly claims less than a signed B+.

A+
C.R.E.E.D.
Self-Reported
B+
C.R.E.E.D.
Signed
?
C.R.E.E.D.
Provisional
<!-- embed your badge --> <img src="https://api.creed-ai.org/api/v1/badge/{your-slug}/overall" alt="C.R.E.E.D. transparency score">

Public reads are unauthenticated. GET /api/v1/orgs/{slug}/scores — no key needed.

PRICING

Nonprofits
$0
always — no cap
  • Everything in Free
  • Unlimited events/day
  • Priority onboarding
  • C.R.E.E.D. Institute backing
  • Verification of nonprofit status required
Volume & SLA
Coming
Phase 3
  • Everything in Free
  • >50k events/day
  • Uptime SLA
  • SIGNED verification tier
  • AUDITED tier (third-party)
  • Trust first, billing second

The movement comes first. Billing is a Phase 3 problem.

FAQ

Can I self-host the scoring provider?
Yes. The kytran-creed repository is the open-source reference implementation. Run it yourself and your events score on your own infrastructure. The schema is the standard, not the host — any scoring provider that implements the schema can score you.
What is the provisional gate?
A score is only published once a feed has ≥100 events across ≥3 pillars spanning ≥14 days. This prevents cherry-picked info events from inflating a grade. Until the gate is cleared, the badge reads PROVISIONAL.
Can I hide my score after it's published?
No. Once your organization is listed in the public directory, the score is permanently visible. You can delist (remove from the directory), but the score history is not hidden. A hideable score is a voluntary commitment — and voluntary commitments fail (see WP-003).
Do events contain personal data?
Events describe systems, never data subjects. The ingest endpoint rejects descriptions or metadata containing emails or phone numbers, and caps metadata at 4 KB. Governance events are about what your AI does, not about the people it serves.
What are the five governance pillars?
Transparency, Fairness, Safety, Privacy, Accountability. Every event is tagged to one pillar. Your per-pillar breakdown is public alongside the overall grade. The full event taxonomy and JSON schema are in the Event Schema spec.
What language or platform does this work with?
Any platform that can make an HTTP POST. The Python client is zero-dependency and works on Python ≥ 3.9. Direct REST integration is straightforward: POST /api/v1/events with a JSON body and Authorization: Bearer creed_sk_…. SDKs for other languages are roadmap items.

Ready to connect?

We onboard organizations by hand while the standard is young — verified identity, real governance commitment, no anonymous placeholders.

Apply to Connect →

Questions? Contact the Institute.  ·  Schema: standard.html  ·  Source: GitHub