Access and authentication
Choose browser approval for research, or a licensed API key for your service.
Two ways to connect
| Connection | Authentication | Intended use |
|---|---|---|
| Hosted MCP | Browser sign-in and read-only approval with a paid Sloe account | Interactive research in a supported assistant |
| HTTP API or direct bearer MCP | Licensed Data Access key | Approved app, service or data workflow |
A Claude or ChatGPT subscription does not include Sloe Data access. Your Sloe account controls Sloe entitlement; model-provider billing remains separate.
Get and manage your key
After purchasing Data Access, sign in with the purchase email and open Account. Complete password setup if prompted. Generate and label a key, then copy it once into your secret store. Up to three active keys let you replace a key before revoking the old one. Revoke an exposed or unused key immediately. Billing and invoices are available from the account Billing button.
If access is not recognized, contact support with your account email and invoice reference. Do not include a key or purchase a duplicate subscription.
API requests
Authorization: Bearer YOUR_DATA_ACCESS_KEYSend this header on every licensed request. Query-string keys are rejected. Ordinary subscriber cookies and admin credentials are not substitutes for a Data Access key.
Store the key in a server-side secret store. Do not use NEXT_PUBLIC_ environment variables, expose it to browser JavaScript, or commit it in an app bundle. Your app authenticates its own users; your backend makes the Sloe request within your license.
Browser sign-in for MCP
Register the hosted connector, then follow its browser sign-in flow. Approve the read-only connection with the Sloe account that has access. The Sloe email does not have to match the email used for your agent client.
Manual bearer configuration is available to Data Access customers whose client supports sending an Authorization header. Use the client's secret storage rather than a public configuration file.
Troubleshooting access
- 401: verify the key or reconnect the MCP session. It may be missing, malformed, revoked or expired.
- 403: check the account entitlement and the feature's access requirements. Retrying the same request will not create a license.
- Public installation succeeds, reads fail: installation configures the client; it does not activate paid access.
See errors and retries. Contact Sloe through your account or info@thecreditunionwire.com without including your key.