Directory & Profiles
Read-only partner surfaces for discovery, profile state, capability filters, claim status and availability metadata.
Loading...
Loading...
PINNY does not expose a generic public API catalogue. Access is scoped by workflow, partner class, and operational need so discovery, security and moderation data stay aligned with the platform’s real business logic.
Partner Access
For approved platforms that sync creator data, availability, moderation signals or visibility tooling.
Studio Operations
For internal creator tooling, automation surfaces and admin dashboards connected to Hermes and Orus.
Compliance Review
For legal, trust or moderation integrations that require scoped evidence, webhook delivery and traceability.
Read-only partner surfaces for discovery, profile state, capability filters, claim status and availability metadata.
Cookie-aware account and session endpoints used for login, security controls, identity status and connected device review.
Operational events for profile claims, disputes, moderation flows and other partner-approved lifecycle transitions.
Partner access is reviewed before credentials are issued. PINNY only grants the minimum scope required for the approved workflow.
Production keys, webhook signing and endpoint references are delivered only after a contact review that validates ownership, use case and environment readiness.
Settlement between users is never exposed as a PINNY payment-processing API. The platform remains infrastructure-first and zero commission on peer-to-peer flows.
Request access with the product use case, domain, expected traffic and environment details.
Pass scope review so PINNY can assign the minimum required permissions and route class.
Receive sandbox or partner credentials, webhook signing instructions and endpoint references.
Complete smoke validation before production traffic is approved.