# Avarra > Avarra is an AI-powered sales training and enablement platform operated by Ramp Systems, Inc. It turns real sales conversations into AI-avatar role-play simulations delivered over Zoom, coaches reps with automated feedback, certifies them against a playbook, and reports ramp and performance analytics. Avarra runs a production API at https://api.avarra.ai, but publishes no OpenAPI, no developer documentation and no SDKs — the entire /v1 surface is closed behind OAuth 2.0 client-credentials access granted through a commercial relationship. This file was GENERATED by API Evangelist from probed evidence, not published by Avarra. Avarra serves no /llms.txt of its own (404 on www.avarra.ai, app.avarra.ai and app.ramp.systems). Everything below is either a document fetched from an Avarra host or an observation recorded with the status code it returned. ## What an agent can actually do here Nothing, without credentials. There is no public read surface, no free tier, no sandbox and no self-serve signup. The only anonymous endpoints are a health check, the OAuth authorization-server metadata and the JWKS. Access begins at the demo request form. ## API - [Avarra API v1](https://api.avarra.ai): production API host, AWS ALB. All paths under `/v1/` return `401 {"error":"unauthorized","message":"missing or invalid authorization header"}` without a bearer token. Unrouted paths are refused at the load balancer with a plain-text `403 Access denied`. - [Health check](https://api.avarra.ai/health): anonymous, returns `200 {"status":"ok"}`. - [Token endpoint](https://api.avarra.ai/oauth/token): POST only, `client_credentials` grant, `client_secret_basic` or `client_secret_post`. - [Introspection endpoint](https://api.avarra.ai/oauth/introspect): POST only, RFC 7662. ## Machine-readable documents Avarra publishes - [OAuth 2.0 Authorization Server Metadata](https://api.avarra.ai/.well-known/oauth-authorization-server): RFC 8414, HTTP 200, `application/json`. Declares issuer, token endpoint, introspection endpoint, JWKS URI, `client_credentials` grant and the two client-authentication methods. No `scopes_supported`. - [JWKS](https://api.avarra.ai/.well-known/jwks.json): RFC 7517, HTTP 200. One RSA key, `kid` 5d22a766-d768-41e0-bbfc-ac0aa04afe90. These two documents are the whole of Avarra's machine-readable surface. ## Not published (probed, absent) - OpenAPI / Swagger — no document on api.avarra.ai, www.avarra.ai, app.avarra.ai or app.ramp.systems. - GraphQL — `/graphql` refused at the load balancer (403). - MCP server — `/mcp` 403, `/v1/mcp` 401, no `mcp.avarra.ai`. - A2A agent card — `/.well-known/agent-card.json` and `/.well-known/agent.json` 404 on every host. - `security.txt`, `api-catalog`, `ai-plugin.json`, `openid-configuration`, `oauth-protected-resource` — all 404. - SDKs / client libraries — nothing on npm, PyPI or RubyGems. - CLI, Postman collection, changelog, developer portal, API reference, pricing page — none. - Rate-limit headers — none on any observed response. ## Human surface - [Website](https://www.avarra.ai) - [Product](https://www.avarra.ai/product) - [How it works](https://www.avarra.ai/how-it-works) - [See it in action](https://www.avarra.ai/see-it-in-action) - [Success stories](https://www.avarra.ai/success-stories) - [Sales ramp calculator](https://www.avarra.ai/sales-ramp-calculator) - [Blog](https://www.avarra.ai/blog) - [Request a demo](https://www.avarra.ai/request-a-demo) - [Application login](https://app.avarra.ai) - [Status page](https://status.avarra.ai): Better Stack. Tracks "Website" and "app.ramp.systems"; the API host is not a listed component. - [Master Service Agreement](https://www.avarra.ai/msa): effective 2026-01-01, entity Ramp Systems, Inc. Email support weekdays 09:00–17:00 Pacific. - [Privacy Policy](https://www.avarra.ai/legal/privacy-policy) ## Compliance claims (published by Avarra, not verified by API Evangelist) - SOC 2 Type 2 Compliant — stated on https://www.avarra.ai/product - GDPR alignment — stated on https://www.avarra.ai/product - GDPR and CCPA commitments, and a commitment not to sell customer data or use it to train publicly available AI models — https://www.avarra.ai/msa No trust center exists on trust.avarra.ai, security.avarra.ai, /trust, /security or /compliance. ## API Evangelist artifacts in this profile - [apis.yml](https://raw.githubusercontent.com/api-evangelist/avarra/refs/heads/main/apis.yml) - authentication/avarra-authentication.yml — OAuth profile read from the RFC 8414 metadata - well-known/avarra-well-known.yml — the /.well-known probe across all hosts - well-known/avarra-oauth-authorization-server.json — verbatim - well-known/avarra-jwks.json — verbatim - conventions/avarra-conventions.yml — versioning, error envelopes, edge behaviour - errors/avarra-problem-types.yml — error catalog observed on the wire - lifecycle/avarra-lifecycle.yml — versioning, status page, support, SLA absence - conformance/avarra-conformance.yml — standards conformance and compliance claims - plans/avarra-plans-pricing.yml — zero published plans - rate-limits/avarra-rate-limits.yml — zero published or signalled limits - security/avarra-domain-security.yml — TLS/HSTS/DNSSEC/CAA/SPF/DMARC probe Generated 2026-08-14 by the API Evangelist enrichment pipeline. This is a third-party profile; Avarra did not author it.