canonical: https://jentic.com/apis/morelogin.com/morelogin

# MoreLogin API

Jentic publishes the only available OpenAPI specification for MoreLogin API, keeping it validated and agent-ready. MoreLogin provides anti-detect browser profile management, cloud phones, and automation tooling used for multi-account workflows, ad verification, and QA testing across isolated browser fingerprints. The exposed Open API endpoint exchanges an API ID and API Key for a short-lived bearer token that authorises subsequent calls into MoreLogin's profile management surface. Agents use this token to script profile orchestration without storing long-lived credentials in tool memory.

## For AI agents

Exchange MoreLogin API ID and API Key credentials for a bearer access token that authorises browser profile and automation calls. Single-endpoint OAuth-style token issuance.

## Scope

Does not handle browser profile creation, cloud phone control, or proxy management - use for MoreLogin bearer-token issuance only.

## Capabilities

- Exchange a MoreLogin API ID and API Key for a bearer access token via the /oauth/token endpoint
- Bootstrap authenticated sessions for downstream MoreLogin profile and cloud phone operations
- Rotate access tokens on a schedule to keep automation pipelines within MoreLogin token lifetimes
- Gate anti-detect browser automation behind a server-side credential exchange instead of embedded keys
- Issue scoped tokens for individual agents or workflows that need MoreLogin browser orchestration

## Use cases

### Anti-Detect Browser Automation Bootstrap

Exchange MoreLogin API credentials for a bearer token before driving browser profiles for multi-account QA, ad verification, or scraping workflows. The /oauth/token endpoint accepts an API ID and API Key and returns the access token used for all downstream MoreLogin calls. This keeps long-lived secrets out of automation runners and lets each job run on a fresh, time-boxed token.

Example prompt: Call POST /oauth/token with the configured MoreLogin API ID and API Key, capture the returned access token, and attach it as a bearer header on the next MoreLogin profile call.

### Token Rotation in CI Pipelines

MoreLogin tokens are short-lived, so CI jobs that orchestrate browser profiles need to refresh credentials between runs. Build automation calls /oauth/token at job start, stores the token in a job-scoped secret, and uses it for the duration of the run only. This prevents stale tokens from breaking long pipelines and avoids checking long-lived API Keys into pipeline configuration.

Example prompt: At pipeline start, request a new MoreLogin bearer token, set it as a masked environment variable, and discard it after the job completes.

### Agent-Driven MoreLogin Orchestration via Jentic

An AI agent that needs to drive MoreLogin browser profiles searches Jentic for the MoreLogin token operation, loads the input schema, and executes the call without ever seeing the underlying API ID and API Key. Jentic's your Jentic One instance holds the credentials and returns only the issued bearer token to the agent's context, so the long-lived secret never enters the prompt.

Example prompt: Search Jentic for 'authenticate to MoreLogin', load the /oauth/token operation, and execute it through Jentic to receive the bearer token needed for downstream browser profile calls.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /oauth/token | Exchange API ID and API Key for a bearer access token |

## Key resources

- **Authentication** — Token exchange endpoint that turns an API ID and API Key into a bearer access token for subsequent MoreLogin calls.

## Why Jentic

- **Setup:** Wiring MoreLogin by hand means exchanging your long-lived API ID and key for a short-lived bearer at /oauth/token and refreshing it before it expires. Through Jentic you install once, import the MoreLogin API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** This spec exposes only token issuance at /oauth/token, so limit the agent to the operation it needs, which is requesting an access token. You choose the operations it may call, so nothing beyond token issuance is included unless you add it.
- **Credential handling:** Your MoreLogin API ID and key are stored once, encrypted, by your own Jentic One instance and exchanged for the short-lived bearer at execution time. The long-lived key never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'authenticate to MoreLogin' or 'get a MoreLogin access token', and Jentic returns the /oauth/token operation with its input schema, so the agent requests a token without reading MoreLogin's docs.

## Related APIs

- **ZenRows API** — ZenRows offers managed scraping browsers and proxy rotation as a hosted alternative to running anti-detect profiles yourself.
- **Twilio API** — Twilio supplies SMS verification numbers commonly used to register accounts inside MoreLogin browser profiles.
- **Slack API** — Slack receives alerts when a MoreLogin token issuance fails or when a profile-driven QA run completes.

## FAQ

### Why is there no official OpenAPI spec for MoreLogin API?

MoreLogin does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MoreLogin API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the MoreLogin API use?

MoreLogin uses bearer token authentication. You first POST your API ID and API Key to /oauth/token, then attach the returned access token as a Bearer header on subsequent calls. Through Jentic, the API ID and API Key live in the encrypted vault and only the short-lived bearer token reaches the agent context.

### Can I manage browser profiles with the MoreLogin API spec on Jentic?

The OpenAPI spec currently covers the /oauth/token credential exchange only. Profile management calls authenticate with the bearer token returned by that endpoint, but their schemas are not yet in this spec. Use the token from /oauth/token with MoreLogin's documented profile routes.

### What are the rate limits for the MoreLogin API?

MoreLogin does not publish public rate limits in its OpenAPI spec. Token issuance via /oauth/token is bounded by MoreLogin's account-level fair-use policy, so agents should cache the returned access token for its lifetime instead of re-requesting on every call.

### How do I authenticate to MoreLogin through Jentic?

Run pip install jentic, then search 'authenticate to MoreLogin' to find the /oauth/token operation, load its schema, and execute. Jentic injects the API ID and API Key from your vault and returns the bearer token to your agent.

### Is the MoreLogin API free?

MoreLogin offers a free tier with paid plans for higher profile counts and team features. The API itself is included with the platform subscription; pricing is per-account, not per-call.

### Can I limit what my agent is allowed to do with the MoreLogin API?

Yes. Because Jentic One is self-hosted, your own rules decide which MoreLogin operations and credentials the agent may use. This spec exposes only token issuance at POST /oauth/token, so you can restrict the agent to requesting an access token and nothing else. Since you choose the operations it may call, no capability beyond that credential exchange is available unless you explicitly add it.