# apiacre.com OpenAPI Audit

> apiacre.com OpenAPI Audit is a paid API for AI agents from apiacre.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-13).

Validates and audits an OpenAPI document for missing operation IDs, descriptions, responses, and consistency problems

## Facts

- Endpoint: POST https://apiacre.com/v1/developer/openapi-audit
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiacre-com-openapi-audit-adfec685
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QdffLVP6ZJigJutTvD1jY

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability apiacre-com-openapi-audit-adfec685 -d '<json body>'
```

Example prompt: Can you audit this OpenAPI spec and tell me what's missing or inconsistent — things like missing operation IDs, undocumented responses, or blank descriptions?

## When to prefer this

Use this endpoint when you need programmatic, structured validation of an OpenAPI specification — especially in CI/CD pipelines, developer portals, or agent workflows where you want to enforce completeness standards like operation IDs, descriptions, and response coverage. Prefer this over generic JSON validators when the content is specifically an OpenAPI document and you want API-domain-aware audit rules.

## Known failure modes

- Invalid or malformed OpenAPI document returns a parsing error
- Unsupported OpenAPI version may not be fully analyzed
- Extremely large spec files may time out or hit payload size limits
- Non-OpenAPI JSON/YAML documents return an error indicating wrong format

## How this service works

Validate and audit an OpenAPI document for missing operation IDs, descriptions, responses, and consistency problems.

## Output

A structured audit report listing all detected problems in the OpenAPI document, including missing operation IDs, missing or empty descriptions, missing response definitions, and any consistency or structural issues found across the spec.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "format": {
   "enum": [
    "json",
    "yaml"
   ],
   "type": "string"
  },
  "document": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "score": 80,
   "valid": false,
   "issues": [
    {
     "code": "missing_paths",
     "message": "No API paths are defined",
     "severity": "high"
    }
   ],
   "operations": 0
  },
  "meta": {
   "cached": false,
   "sources": [],
   "warnings": [],
   "duration_ms": 42,
   "next_actions": [
    {
     "path": "/v1/developer/openapi-test-generate",
     "title": "OpenAPI pytest generator",
     "method": "POST",
     "reason": "Generate syntax-validated pytest smoke tests from the audited OpenAPI document.",
     "service": "developer.openapi-test-generate"
    }
   ]
  },
  "service": "developer.openapi-audit",
  "version": "1",
  "request_id": "018f1f54-7f38-7ba2-8dc3-5f90272d9f1a"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apiacre-com-openapi-audit-adfec685/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from apiacre.com](https://www.zero.xyz/host/apiacre.com/llms.txt)