1
Register the integration
Define the app name, owner, support contact, purpose and current version.
DEVELOPER CENTER LIVESCOPED ACCESS • REVIEW • AUDIT
AEUC Developer Platform
A real integration path from idea to approved production access.
The Developer Center ties together permissions, SDK contracts, provider connection requests, EAGLE Builder and the working app review intake so developers always know what comes next.
INTEGRATION LIFECYCLE
Eight steps. No mystery states.
WORKING SUBMISSION + CONNECTION REQUESTS ENABLED
2
Choose permissions
Request only the AEUC scopes needed for the workflow and understand the risk level.
3
Prepare security + privacy
Document credential storage, data handling, retention, incident contact and privacy policy.
4
Test in sandbox
Verify authentication, rate limits, retries, webhooks, failure handling and scope boundaries.
5
Submit for review
Send the real app through AEUC review and receive a tracked review ID.
6
Move to production
Only approved integrations should receive production credentials or provider authorization.
7
Operate responsibly
Version releases, monitor failures, rotate credentials and keep support contacts current.
8
Stay revocable
Users and AEUC should be able to disable access when permissions or trust change.
BUILDER CONTROL
EAGLE Builder
Inspect project readiness, agent capabilities, integrations, approval boundaries and the guarded build-to-deploy workflow.
Open Builder →WORKING NOW
Connection Requests
Users can request supported providers and declare the access they need through the Connected Apps center.
WORKING NOW
App Review Intake
Developers can submit app details, security notes, privacy handling, version and requested scopes into a tracked AEUC review record.
CONTRACT PUBLISHED
SDK + OAuth Model
The extension contract is published now; production OAuth/client issuance should only be labeled live after the final credential registry and revocation backend are implemented.