The open child-safety API. One spec. 229 platforms.

PCSS v1, MCP server, TypeScript SDK, REST. Build COPPA, KOSA, EU DSA, and 64 other child-safety frameworks into your product with a single integration — not 67.

Get API keys Read the docs

quickstart.sh

curl https://phosra-api.fly.dev/v1/policies \
  -H "Authorization: Bearer $PHOSRA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "child_id": "child_abc123",
    "rule_categories": ["content_rating", "screen_time", "web_filter"],
    "platforms": ["netflix", "youtube", "roblox"]
  }'

One call. Policies pushed to every connected platform.

Civil-society standards bodiesDesign partner candidate

NCMEC + INHOPEIn conversation

ESRB / MPAA / PEGI

Bark · Aura · Canopy · Pinwheel

Apple / Google OS age signalIn conversation

Why an open spec

Child safety is too important to be a proprietary API.

PCSS v1 — the Phosra Child Safety Spec — is the open technical standard that maps statutory requirements to enforceable platform actions. We publish it. You build against it. Other vendors can implement it. The infrastructure layer for child safety should be neutral, like TCP/IP — not locked behind one SaaS contract.

Surface area

Four ways to integrate. Pick what fits your stack.

REST API

Versioned, OpenAPI-documented endpoints for policies, rules, children, families, platforms, and standards. SDKs auto-generated from the spec.

API reference

MCP server

Native Model Context Protocol server — drop Phosra into Claude, Cursor, or any MCP-compatible agent and let it reason about compliance and parental controls directly.

MCP setup

TypeScript SDK

First-class @phosra/sdk for Node, Bun, and edge runtimes. Full types for all 45 rule categories and 67-law registry. Tree-shakeable.

SDK docs

Open spec

PCSS v1 is publicly documented and citable. No vendor lock-in — if Phosra disappeared tomorrow, the spec lives on.

Read the spec

MCP-native

Drop Phosra into your agent in 30 seconds.

The Phosra MCP server exposes every API surface as a typed tool call — so Claude, Cursor, or any MCP client can reason about COPPA compliance, generate policies, and push enforcement changes without you wiring the REST glue yourself.

MCP setup guide

.mcp.json

{
  "mcpServers": {
    "phosra": {
      "command": "npx",
      "args": ["-y", "@phosra/mcp"],
      "env": {
        "PHOSRA_API_KEY": "phk_..."
      }
    }
  }
}

Free API keys. No card on file.

Sandbox + production environments. Full SDK. MCP server. The spec. Build a compliance feature in an afternoon — deploy it to production this week.

Get API keys Read the docs GitHub