Skip to main content

Risk Tape v1 — Overview

A Risk Tape is a standardised JSON document that encapsulates everything a lender needs to underwrite a creator. CreatorLayer builds it automatically from connected platform data.

Top-level structure

SectionPurpose
schema_versionSemantic version of the tape format (1.0.0)
as_of_dateSnapshot date — all metrics computed as of this date
obligorCreator identity: ID, jurisdiction, entity type, KYC status
platform_connectionsWhich platforms are connected, their role and data quality
cashflow_summaryAggregated revenue: 30d, 90d, monthly time series
risk_profileComputed metrics: volatility, drawdown, concentration, etc.
eligibilityPer-product decisions: eligible? tier? max advance?
data_qualityCompleteness score (0–100) and quality flags
status"success" or "failed" (set by the JSON schema validator)

Who sees the tape?

  • Lender API integration — consumes the JSON programmatically
  • Lender risk team — reviews via the tape viewer UI or raw JSON
  • Creator — can request a copy via GDPR export (GET /api/v1/gdpr/export)
  • CreatorLayer ops — monitors via /monitor/* endpoints

Tape lifecycle

1. Lender calls POST /api/v1/verifications
2. CreatorLayer sends consent email to creator
3. Creator grants OAuth access to platforms
4. CreatorLayer fetches platform data
5. Risk Tape is built: metrics → eligibility → data quality → validation
6. Tape is returned to the lender (and stored for audit)
7. Webhook fires to lender's callback URL

Schema versioning

The schema_version field uses semantic versioning:

  • Patch (1.0.x): bug fixes, no field changes
  • Minor (1.x.0): new optional fields added
  • Major (x.0.0): breaking changes — fields removed or types changed

Lenders should always check schema_version before parsing.