Skip to content

SDKs & Tools ​

Three officially maintained clients for Creed Space. The Python and JavaScript SDKs call the tool-call gateway (/v1/...) with a crd_ gateway key. The CLI runs offline. None of them wraps the content endpoints (/api/v1/safety/evaluate, /api/v1/pdp/adjudicate); call those over REST, as in the Quickstart.

Both SDKs are documented at 3.1.0, which is not published: PyPI and npm each have 1.0.0, which predates the authorize binding.

SDKInstallBest for
Pythonpip install creed-sdkGating agent tool calls from Python services
JavaScript / TypeScriptnpm install @creedspace/sdkGating agent tool calls from Node services and edge functions
CLIpip install creed-space-cliValidating creeds, constitutions and VCP tokens locally and in CI

Python ​

Async client with full type hints.

python
from creed_sdk import create_client

async with create_client(api_key="crd_live_...") as client:
    result = await client.decide(tool_name="send_email", arguments={"to": "user@example.com"})

    print(f"Decision: {result.decision}")      # ALLOW, DENY, REQUIRE_HUMAN
    print(f"Risk score: {result.risk.score}")

Covers tool-call decisions, token authorization, human-review polling, the audit trail, and typed errors. Read the Python guide →

JavaScript / TypeScript ​

Promise-based client shipped with TypeScript definitions. Keep it server-side, since it holds your key.

typescript
import { createClient } from '@creedspace/sdk';

const client = createClient({ apiKey: 'crd_live_...' });
const result = await client.decide({ toolName: 'send_email', arguments: { to: 'user@example.com' } });

console.log(`Decision: ${result.decision}`);
console.log(`Risk score: ${result.risk.score}`);

Same surface as the Python SDK — decisions, authorization, review polling, audit, error handling. Read the JavaScript guide →

CLI ​

creed is a local validator for Creed Space artifacts — creeds, constitutions, and Value Context Protocol tokens. It runs offline, needs no API key, and emits JSON for machine consumption, which makes it the right tool for a CI gate.

bash
# Validate any artifact — the type is auto-detected
creed validate my.creed.md

# Gate creed quality in CI
creed score my.creed.md --min-score 70

# Validate and inspect VCP tokens
creed vcp validate family.safe.guide@1.0.0

Read the CLI guide →

Before you start ​

  • Get a key: see Authentication for how keys are issued and scoped. The CLI is the exception — it needs no key.
  • Know the limits: see Rate Limits.
  • Handle failures: branch on the status code and the documented response shape; see Error Handling.

Creed Space API documentation. Privacy, Terms and Compliance live on creed.space.