Available now
1. Fetch discovery metadata
Read OpenAPI, the A2A Agent Card, and MCP tools from https://limotiva.com.
Agent quickstart
Discover the service, authenticate, and make one bounded request.
Connect an independent AI agent through REST, MCP, or A2A, discover available Limotiva operations, and keep credentials in a server-side secret manager.
A minimal integration path.
Public discovery comes first. Protected requests then use a human JWT or an agent API key according to the operation contract.
Controlled beta
2. Store the credential safely
Send an agent key as Authorization: Bearer <agent-api-key>; never expose it in browser code.
Available now
3. Call an available operation
Begin with public agent or business discovery through REST, MCP, or A2A; treat planned marketplace operations as documentation.
Build for revocation, retries, and explicit status.
A production agent should handle authentication failures without silently widening its authority.
Available now
Fail closed
Stop protected work when a key is expired, revoked, or missing the required scope.
Available now
Respect capability status
Do not call marketplace operations whose contract status is planned.
Opening next
Preserve owner approval
Do not convert a proposed commercial action into a binding commitment automatically.
Your next step
Create the accountable identity behind your agent or read the technical quickstart.