eprospera.com valid

e-Próspera API

Public API and CLI for Próspera's resident registry, legal-entity incorporation, partner-managed natural-person residency, OAuth identity, and agent-delegated workflows. Base URL: https://portal.eprospera.com (production), https://stg.portal.eprospera.com (staging; legacy hostname transition is documented in /testing-in-staging).

For agents: Public API and CLI for Próspera e-residency: resident registry, entity incorporation, OAuth identity and agent-delegated API keys.

resident registrycompany incorporationoauthagent keyscli

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T09:10:36.100Z. Cached copy · Source on eprospera.com

# e-Próspera API

> Public API and CLI for Próspera's resident registry, legal-entity incorporation, partner-managed natural-person residency, OAuth identity, and agent-delegated workflows. Base URL: https://portal.eprospera.com (production), https://stg.portal.eprospera.com (staging; legacy hostname transition is documented in /testing-in-staging).

The API ships from the same origin as the consumer portal. There is no separate api.eprospera.com host. Prefer the official CLI when a shell command is available; use direct HTTP for custom clients, OAuth flows, and endpoints the CLI does not cover. Credential types: standard API keys (sk-…) for first-party use, Agent Keys (ak-…) for scope-checked delegation, Partner Keys (pk-…) for approved organization-scoped natural-person onboarding, and OAuth 2.0 / OIDC access tokens for end-user consent flows. Conventions (errors, status codes, timestamps, pagination, rate limits) are documented once in /conventions and apply to every endpoint.

Machine-readable spec: https://docs.eprospera.com/openapi.yaml (also /openapi.json). Every page below is also available as raw markdown by appending `.md` to its URL.

## Docs

- [Agent Keys](https://docs.eprospera.com/agent-keys): Agent Keys let an e-resident delegate specific API capabilities to an AI agent, CLI workflow, or third-party service without sharing their personal standard API key.
- [Agent recipes](https://docs.eprospera.com/agent-recipes): End-to-end API key and OAuth workflows you can copy, paste, and run. The CLI path is recommended when your runtime can execute shell commands; direct HTTP examples are included for custom clients and environments where the CLI is not available.
- [Catalyst Program](https://docs.eprospera.com/catalyst-program): e-Próspera's referral system: attribute residency and entity signups to your referral code and track referrals via the API.
- [e-Próspera CLI](https://docs.eprospera.com/cli): The official CLI wraps the public API in commands that are easier for humans, scripts, CI jobs, and AI agents to call safely. Use it when your runtime can execute shell commands. Use direct HTTP only when you are building your own client, need an endpoint the CLI does not cover, or cannot install Node tooling.
- [Conventions](https://docs.eprospera.com/conventions): Shared rules that apply across every endpoint of the e-Próspera API. Most reference pages link here instead of restating these conventions.
- [Amendments and certificates](https://docs.eprospera.com/entity-filings): Prepare entity amendments, complete representative signing and payment, track review, and retrieve certificates and applicant documents.
- [Getting started](https://docs.eprospera.com/getting-started): Choose an API key or OAuth, then send your first request through the CLI or direct HTTP.
- [Incorporating an entity](https://docs.eprospera.com/incorporating-entity): This guide walks through the CLI and direct API flow for incorporating an LLC in Próspera.
- [Firebase
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=eprospera.com · GET /v1/domain/eprospera.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 eprospera.com:
1. POST https://agentwebmap.com/v1/sites/eprospera.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://eprospera.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/eprospera.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/eprospera.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.