outseta.com valid

Outseta API

REST API reference for Outseta — the all-in-one platform for SaaS founders.

For agents: Outseta REST API reference for an all-in-one SaaS platform covering auth, billing, user accounts, CRM email and support, plus a remote MCP server.

rest apisaas billingauthenticationcrmmcp server

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T11:45:30.297Z. Cached copy · Source on outseta.com

# Outseta API

> REST API reference for Outseta — the all-in-one platform for SaaS founders.

- [Introduction](https://docs.outseta.com/index.md): REST API reference for Outseta — auth, billing, user accounts, email, and support, all in one platform.
- [Authentication](https://docs.outseta.com/essentials/authentication.md): How to authenticate requests to the Outseta API.
- [MCP server](https://docs.outseta.com/mcp-server.md): Connect your AI agent to Outseta with the remote MCP server — manage your account and analyze your business data directly.
- [Agent skills](https://docs.outseta.com/agent-skills.md): Wire Outseta into your app with the Outseta agent toolkit — integration as simple as writing a prompt.
- [Log a user in.](https://docs.outseta.com/api-reference/public/log-a-user-in.md): Authenticates a user and returns a JWT access token (plus a refresh token).
- [Exchange a magic-link token for an access token (passwordless login).](https://docs.outseta.com/api-reference/public/exchange-a-magic-link-token-for-an-access-token-passwordless-login.md): Call this with the magicToken carried by the link from a "magic link" email (requested via POST /api/v1/crm/people/requestMagicLink):
- [Complete login when user has two-factor authentication enabled.](https://docs.outseta.com/api-reference/public/complete-login-when-user-has-two-factor-authentication-enabled.md): Call this after `POST /api/v1/tokens` returns `two_factor_required`. Post the challenge token from that response together with the user's one-time code (the emailed code, or the current code from their authenticator app):
- [Re-send the one-time code for an in-progress email two-factor challenge.](https://docs.outseta.com/api-reference/public/re-send-the-one-time-code-for-an-in-progress-email-two-factor-challenge.md): Post the challenge token from the original `POST /api/v1/tokens` response:
- [Complete login with a two-factor recovery code.](https://docs.outseta.com/api-reference/public/complete-login-with-a-two-factor-recovery-code.md): A fallback for users who cannot produce their primary code but still have a recovery code on file (see `recovery_codes_available` on the login response). Post the challenge token together with one recovery code:
- [Switch an in-progress login challenge to a different enrolled mechanism.](https://docs.outseta.com/api-reference/public/switch-an-in-progress-login-challenge-to-a-different-enrolled-mechanism.md): When a user has more than one method enrolled (see `available_mechanisms` on the login response) they can switch the active challenge — for example from `Totp` to `Email` when they have lost access to their authenticator. Post the current challenge token and the desired mechanism:
- [Begin email enrollment during a forced-2FA login.](https://docs.outseta.com/api-reference/public/begin-email-enrollment-during-a-forced-2fa-login.md): Call this when `POST /api/v1/tokens` returned `two_factor_enrollment_required` and the user chooses email. Post the enro
…

Related sites

Find similar publishers by meaning →

Other listed sites in APIs and SDKs. See the whole category →

Machine-readable: GET /v1/resolve?q=outseta.com · GET /v1/domain/outseta.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for outseta.com:
1. POST https://agentwebmap.com/v1/sites/outseta.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://outseta.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/outseta.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/outseta.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.