TRUST · DEVELOPER PLATFORMS
Developer platform API disclosure
How AGEIS connects external creator platforms, what it reads, how provider approvals are handled, and which capabilities remain disabled until the provider authorizes them.
Bounded channel, video and owner-authorized data
AGEIS uses Google OAuth and YouTube APIs only for scopes the account owner grants. Data API ingestion is bounded and source-attributed. A separately governed private-first publishing lane may use the upload scope only after explicit publishing and rights gates. Extended quota, additional derived-metric privileges and extended eligible public-statistical retention stay disabled until YouTube approves them.
Read and insights connection by default
The default Meta connection requests Page/Instagram read and insights permissions, not publishing permissions. AGEIS targets the current Graph API contract and records provider-returned data, pagination and usage telemetry. Features that require Advanced Access or App Review remain unavailable to production users until Meta grants that access.
Display API read lane
The default TikTok connection requests basic account identity and video-list access. AGEIS follows TikTok's returned cursor and refresh-token rotation. Direct/public posting is a separate provider-approved capability and is not represented as enabled by a successful read connection.
Restricted member-social access
AGEIS uses the LinkedIn OAuth and versioned REST contracts for authorized member data. Restricted scopes and programmatic refresh are treated as provider-controlled privileges. If the app is not enabled for them, AGEIS keeps the affected capability unavailable rather than substituting test or cached data.
Provider truth over catalog claims
A connector is considered production-ready only after its real OAuth round trip, permissions, token lifecycle and API reads are proven. Code presence or a catalog entry alone is not treated as provider approval. Uncertified capabilities remain visibly blocked.
No invented quota or silent provider success
AGEIS honors provider rate-limit responses, bounded retries and provider-returned pagination. Provider-specific portal limits remain authoritative. A 401, 429, provider error, malformed successful response or missing required scope is recorded as a real failure/degraded state; it is never converted into empty successful data.
Consent stays scoped to the connected workspace
OAuth credentials are sealed server-side. Connected data is tenant-scoped and governed by account export, disconnect and deletion controls. AGEIS does not ask for platform passwords and does not claim access beyond the scopes and provider approvals actually granted. See the Privacy Policy, Terms and Data Rights.