Portal Authentication
How people sign in in the browser - and how that fits with developer API keys, Agent Credentials, and Automation.
Updated October 3, 2026
This guide explains who signs in where. Integrations on your servers use developer API keys, not the same session used to log into https://ugc.africa in a browser.
Choose the right authentication path
| What you are doing | How to authenticate |
|---|---|
| Server-side campaign, slot, wallet, or webhook integration | Authorization: Bearer UGSK_live_... - API key authentication |
| Zapier / Make / n8n / custom automation | Automation connection API key (UGAU_...) or OAuth - Automation |
| AI agent initiating money movement on your behalf | Agent Credential (agcred_...), scoped to agent/transfer, agent/balance, agent/payment-link - Agent Credentials |
| AI model orchestrating campaign/slot/wallet workflows via tool calls | End-user JWT or automation OAuth access token, plus the mcp_server entitlement - MCP server. OAuth tokens are scope-limited; the portal JWT is not. |
| Running your account in the browser | Sign in at https://ugc.africa. Manage API keys, webhooks, and settings from the product UI and Developer Console. |
Products that embed UGC
Prefer documented surfaces (UGSK_ REST, Automation, MCP, Agent Credentials) and official UIs. That keeps upgrades predictable and support straightforward.
Did this solve your problem?