Levo

Levo provides an AI‑powered API security platform that protects both traditional APIs and emerging AI‑driven services. The solution offers runtime visibility, threat detection, red‑teaming, and governance across the entire application stack, integrating with CI/CD pipelines and supporting compliance for industries such as banking, insurance, healthcare, and retail. Levo’s platform unifies API and AI security, delivering real‑time risk insights, automated policy enforcement, and detailed reporting to help organizations secure complex, dynamic micro‑service architectures and AI models.

Levo is profiled on the APIs.io network. Tagged areas include Company, Security, AI, API, and Platform.

Levo’s developer surface includes getting-started guide, changelog, authentication, documentation, engineering blog, pricing, and 8 more developer resources.

21.5/100 emerging Agent 5/100 agent aware Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →
0 APIs
CompanySecurityAIAPIPlatform

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Levo It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/levo/"><img src="https://apis.io/badge/levo/card.svg" alt="Levo on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
  • MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
  • Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
11 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/levo/apis.yml: open an issue on github.com/api-evangelist/levo to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Levo Authentication

1 scheme

SECURITY

Levo Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: levo
name: Levo
image: https://cdn.prod.website-files.com/68d0ca01084046ac052b0d8d/68e354afe74b7b9c68f91e54_d5889fa56eef309d6a1e006a97e83701_Levo%27s%20Open%20Graph%20Logo.svg
description: Levo provides an AI‑powered API security platform that protects both traditional APIs and emerging AI‑driven
  services. The solution offers runtime visibility, threat detection, red‑teaming, and governance across the entire application
  stack, integrating with CI/CD pipelines and supporting compliance for industries such as banking, insurance, healthcare,
  and retail. Levo’s platform unifies API and AI security, delivering real‑time risk insights, automated policy enforcement,
  and detailed reporting to help organizations secure complex, dynamic micro‑service architectures and AI models.
url: https://raw.githubusercontent.com/api-evangelist/levo/refs/heads/main/apis.yml
x-type: company
x-source: harvest:g2-catalog
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-21 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-21'
modified: '2026-10-21'
tags:
- Company
- Security
- AI
- API
- Platform
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: TermsOfService
  url: https://www.levo.ai/terms-and-conditions
- type: PrivacyPolicy
  url: https://www.levo.ai/privacy-policy
- type: GettingStarted
  url: https://docs.levo.ai/quickstart
- type: ChangeLog
  url: changelog/levo-changelog.yml
- type: Authentication
  url: authentication/levo-authentication.yml
- type: Hosts
  url: hosts/levo-hosts.yml
- type: Vendors
  url: vendors/levo-vendors.yml
- type: GitHubOrganization
  url: https://github.com/levoai/
- type: ChangeLog
  url: https://docs.levo.ai/changelog
- type: DomainSecurity
  url: security/levo-domain-security.yml
- type: Website
  url: https://levo.ai/
- type: Documentation
  url: https://www.levo.ai/
- type: Blog
  url: https://www.levo.ai/resources/blogs
- type: Pricing
  url: https://www.levo.ai/pricing
apis: []
x-enrichment:
  date: '2026-10-21'
  status: enriched
  artifacts_added: 8
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Levo API — frequently asked questions

How do I authenticate with the Levo API?

Levo uses bearer-token authentication (1 scheme). The details are profiled on APIs.io as Levo Authentication.

Is the Levo API ready for AI agents?

Levo has a Kin Score of 21.5 out of 100 (emerging) and an Agent Readiness score of 5.4 (agent-aware), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/levo"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/levo/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/levo/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.