Visibility (GleefulAI)

Visibility is an AI-visibility and answer-engine-optimization audit API from GleefulAI. It scores how visible and understandable a website is to AI assistants and agents, then generates the artifacts to improve it — audit scoring at three depths, fix generation, competitor gap and suggestion comparison, bot-access auditing, citation checking, and generation of `llms.txt` and schema markup. The unusual part is payment: there are no API keys at all. Access is metered per call through x402 micropayments in USDC on Base, so a caller pays per request rather than registering. That makes it callable by an agent with a wallet and no signup flow.

Visibility (GleefulAI) publishes 1 API on the APIs.io network: Visibility AI Audit API. Tagged areas include AI Visibility, Answer Engine Optimization, AEO, Website Audit, and Agent-native.

Visibility (GleefulAI)’s developer surface includes documentation and 4 more developer resources.

18.1/100 emerging ▬ flat Agent 16/100 agent aware Full breakdown ↓
scored 2026-08-05 · rubric v0.9.1
1 APIs
AI VisibilityAnswer Engine OptimizationAEOWebsite AuditAgent-nativex402Micropaymentsllms.txtDeveloper Tools

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-05 · rubric v0.9.1
Composite quality — 18.1/100 · emerging
Contract Quality 9.7 / 25
Developer Ergonomics 1.7 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.7 / 10
Agent readiness — 16/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/gleefulai-visibility: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Visibility AI Audit API

Audits how visible a website is to AI assistants and agents. 36 operations across 22 paths — every path answers both GET and POST — covering audit scoring at score/full/deep dep...

Resources

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
name: Visibility (GleefulAI)
description: 'Visibility is an AI-visibility and answer-engine-optimization audit API from GleefulAI. It scores how visible
  and understandable a website is to AI assistants and agents, then generates the artifacts to improve it — audit scoring
  at three depths, fix generation, competitor gap and suggestion comparison, bot-access auditing, citation checking, and generation
  of `llms.txt` and schema markup. The unusual part is payment: there are no API keys at all. Access is metered per call through
  x402 micropayments in USDC on Base, so a caller pays per request rather than registering. That makes it callable by an agent
  with a wallet and no signup flow.'
url: https://gleefulai-visibility.apievangelist.com/apis.yml
created: '2026-08-02'
modified: '2026-08-02'
specificationVersion: '0.21'
tags:
- AI Visibility
- Answer Engine Optimization
- AEO
- Website Audit
- Agent-native
- x402
- Micropayments
- llms.txt
- Developer Tools
apis:
- name: Visibility AI Audit API
  description: 'Audits how visible a website is to AI assistants and agents. 36 operations across 22 paths — every path answers
    both GET and POST — covering audit scoring at score/full/deep depths, fix generation, competitor comparison and gap analysis,
    bot-access auditing, citation checking, and generation of llms.txt and schema markup. OpenAPI 3.1.0. No API keys: access
    is paid per call via x402 micropayments in USDC on Base.'
  humanURL: https://visibility.gleefulai.com/docs
  baseURL: https://visibility.gleefulai.com
  tags:
  - AI Visibility
  - Answer Engine Optimization
  - Website Audit
  - x402
  - Agent-native
  properties:
  - type: OpenAPI
    url: openapi/gleefulai-visibility-openapi.json
  - type: OpenAPI
    url: https://visibility.gleefulai.com/openapi.json
  - type: Documentation
    url: https://visibility.gleefulai.com/docs
common:
- type: Website
  url: https://visibility.gleefulai.com
- type: Documentation
  url: https://visibility.gleefulai.com/docs
- type: LLMSTxt
  url: llms/gleefulai-visibility-llms.txt
- type: LLMSTxt
  url: https://visibility.gleefulai.com/llms.txt
- type: Company
  url: https://gleefulai.com
maintainers:
- FN: GleefulAI
  url: https://gleefulai.com
x-evidence:
  harvested: '2026-08-02'
  request: apisio/apis.io#45
  probes:
  - https://visibility.gleefulai.com/openapi.json -> HTTP 200, OpenAPI 3.1.0, 22 paths / 36 ops
  - https://visibility.gleefulai.com/llms.txt -> HTTP 200, 2,072 bytes, text/plain
  - https://visibility.gleefulai.com/docs -> HTTP 200
  - https://visibility.gleefulai.com/nonexistent-xyz789 -> HTTP 404 (no catch-all; the 200s are real)
  - https://visibility.gleefulai.com/.well-known/api-catalog -> HTTP 404
  - https://visibility.gleefulai.com/apis.json -> HTTP 404
  defects_found:
    no_schemas: 36 operations and zero `components.schemas`. Request and response bodies are undescribed, which is the largest
      gap in the contract.
    version_reads_prerelease: '`info.version` is 0.1.0 on a document declaring OpenAPI 3.1.0. Anything parsing the API''s
      own version reads it as pre-release.'
  not_asserted:
    pricing: Access is x402 micropayments in USDC on Base, per the spec description and the submission. No machine-readable
      rate card or per-call price list was found, so plans and rate limits are not asserted.
  note: Submitted by mohammed-mlh on the legacy apisio/apis.io repo, which is a deprecated channel that people still find.
    Slug carries the parent company because "visibility" alone is far too generic for a catalog namespace keyed on provider.