Developer Portal
Integration surface for DSPs, distributors, labels, rights organizations, and music technology partners.
- API architecture
- Sandbox → production path
- Standards versioning
AIMI Platform
Integration mark for products that consume AIMI verification, classification, registry, or instant-label infrastructure. It identifies the technology source; it does not itself mean the partner has passed AIMSO integration certification.
Certification mark for an integration that completes defined metadata, disclosure-label, audit-log, webhook, and security readiness checks against a named AIMSO standards version.
Enterprise Surface
Integration surface for DSPs, distributors, labels, rights organizations, and music technology partners.
Environment-scoped credentials with hashed-at-rest key records, scopes, revocation, and expiry controls.
Enterprise identity layer for each organization integrating with AIMI infrastructure.
Entitlement layer separating commercial plans from API usage and standards access.
Structured entry point for track metadata, AI disclosure, creation method, rights, voice, and ownership declarations.
Returns AIMI verification signals using disclosures, registry data, provenance, rights evidence, and review status.
Standardized machine-readable payload for downstream DSP disclosure and trust labels.
Partner endpoints for verification changes, review events, label changes, and certification updates.
Auditable event stream for API requests, results, territory, standards version, latency, and billable units.
Production-readiness gate validating metadata, label payloads, logging, webhooks, and security requirements.
Certification records for organizations that use AIMI infrastructure or pass AIMSO integration standards.
Partner-facing usage, verification, disclosure-match, and operational reporting by billing period.
Usage-based commercial layer for calls, detections, verifications, registry writes, labels, and webhook delivery.
Core API Contract
Organization identity, subscription entitlements, environment and scopes are checked.
Metadata, disclosure, AI involvement, voice and rights declarations enter the intake contract.
Registry, verification, classification and evidence signals are resolved against a standards version.
DSP receives a normalized disclosure/verification payload for its own consumer-facing UI.
Request, outcome, standards version, territory and billable units are written to the audit stream.
Monthly reporting and metering summarize activity without replacing the underlying event history.
{
"aimi_id": "AIMI-TRACK-00018472",
"ai_music": true,
"ai_classification": "H4",
"disclosure_verified": true,
"voice_status": "authorized",
"aimso_status": "gold_verified",
"standards_version": "AIMSO-1.0",
"ui_label": "AI-LED • VERIFIED"
}Versioned records
State changes remain auditable rather than silently replacing history.
Credential hygiene
Key records are designed around hashes, scopes, environments, expiry and revocation.
Founding Enterprise Program
The current release establishes the enterprise architecture and data contracts. Public production API issuance should follow sandbox validation, authentication hardening, rate limits, billing-provider integration, and an approved AIMSO certification test suite.