Skills for AI Agents

If you are the developer wiring an agent up to e-Próspera, paste this page (or /llms-full.txt) into your agent's system prompt or skill folder.

Official CLI: Honduras-Prospera-inc/eprospera-cli.

TL;DR — what an agent must internalize before the first call

• Use the CLI first when shell access is available: eprospera --json --yes <group> <command>.
• Docs, in order: CLI (install, auth, exit codes) → Standard API Keys, Agent Keys, or OAuth (credentials & scopes) → Conventions (HTTP rules) → this page (capabilities & dead ends) → Agent recipes (copy-paste workflows).
• Every Agent Key request is scope-checked. CLI exit code 4 or HTTP 403 means the key is missing the scope, not that the resource is absent.
• A 404 / CLI exit code 5 from legal-entity reads usually means "created outside the API", not "no such entity." Agent Keys can only see API-created records — see Why your call might return empty.
• Consented entities and tax records require OAuth. They are read-only and limited to the signed-in user or selected entities the user still represents.
• There are no webhooks. Use eprospera application watch <id> --timeout 30m or poll the direct API — see Polling, not webhooks.

Invocation Rules

Prefer this shape for automation:

eprospera --json --yes <group> <command>

• Parse stdout as JSON. Treat stderr as diagnostics.
• Use --raw when compact single-line JSON is better.
• Use --fields id,statusId,name to reduce read responses.
• Use --dry-run before write commands while constructing request files.
• Put credentials in --api-key, EPROSPERA_API_KEY, or auth login; never echo tokens.
• Use EPROSPERA_ENV=staging for staging checks.
• Use direct HTTP only when the CLI does not cover the task or you are implementing your own client.

CLI Capability Matrix

Direct HTTP Mapping

When you cannot use the CLI, call the underlying endpoints directly. All paths are relative to https://portal.eprospera.com in production or https://staging-portal.eprospera.com in staging.

The legal-entity portfolio and tax endpoint families are OAuth-only. Agent Keys cannot use them. Consent limits entity access to the user's selection, and the corresponding personal or entity tax scope is required for every tax request.

Decision Tree — Pick the Right Command

Walk this top-down. Stop at the first row that matches your goal.

1. You need to store or inspect credentials. → eprospera auth login, eprospera --json auth whoami, or eprospera --yes auth logout.

2. You have an RPN string and want to know if it is real and active. → eprospera --json entity verify <rpn>.

3. You have a human-readable name or partial RPN and want to find the entity. → eprospera --json entity search "<query>". If results are empty, broaden the query — do not retry the same input.

4. You have a legal-entity ID that your own agent created earlier. → eprospera --json entity get <id>.

5. You have a legal-entity ID from outside this API. → Not reachable with an Agent Key. A standard sk- key can still entity get any entity you currently represent. Otherwise use OAuth and /api/v1/me/legal-entities/{id}. Do not retry the Agent Key call.

6. You want data about the human who owns the Agent Key or OAuth credential. → eprospera --json me profile, me residency, or me id-verification with the matching scope.

7. You want entities the OAuth user selected during consent. → eprospera --json me legal-entities list, then get or documents with a returned ID.

8. You want personal or consented-entity tax data. → Log in with OAuth, then use tax status, tax list, tax get, or tax download. Use --subject personal or a consented entity UUID.

9. You want to incorporate a new LLC. → See Recipe 2. Confirm MoW, pre-accepted AOC, and a fully covering voucher before the agent starts.

10. You want the resident to pay through hosted checkout. → Use application checkout with a standard key. Agent Keys cannot create checkout sessions.

11. You want to know when an application is approved. → eprospera --json application watch <id> --timeout 30m.

12. You need referral attribution or a public visitor pass. → Use referral list with a standard key or visitor-pass create without a credential.

13. You need exact wire-level request and response shapes. → Use the direct HTTP reference pages.

Why Your Call Might Return Empty

Read this section any time a response is unexpectedly empty, 404, CLI exit code 5, 401, 403, or CLI exit code 4. Most of these are by design, not bugs.

Polling, Not Webhooks

There are no webhook callbacks today. Prefer the CLI watcher:

eprospera --json application watch <application-id> --timeout 30m

Direct HTTP callers should poll GET /api/v1/legal_entity_applications/{id} every 30 seconds for the first 2 minutes, then back off to every 5 minutes. Approved and Rejected are terminal — stop polling.

Machine-Readable Resources

If your agent has fetch capability, ingest these instead of scraping rendered pages:

• Official CLI — source repository for the e-Próspera CLI.
• CLI package on npm — current published version and installation metadata.
• CLI releases — changelog and standalone bundles.
• /llms.txt — short Markdown index of every doc page, per the llms.txt standard.
• /llms-full.txt — CLI commands, endpoints, scopes, request/response shapes, and conventions in one plain-text file.
• /openapi.yaml — OpenAPI 3.1 spec for direct HTTP clients.

Where To Go Next

• Use the CLI: CLI — install, authenticate, command matrix, exit codes.
• Pick credentials: Standard API Keys for first-party sk- access; Agent Keys for scoped delegation.
• Copy a workflow: Agent recipes — CLI and HTTP flows for registry lookup, incorporation, profile reads, and OAuth tax data.
• Build direct HTTP clients: Conventions and the reference pages.
• Sign in with e-Próspera: OAuth overview.
• Read consented entities and taxes: Tax and legal-entity data.