# InfluxData — API Agent Score

> Score: 68/100 (Grade: C) | Domain: influxdata.com | Rubric: 1.0.0 | Checked: July 29, 2026

InfluxData scored 68/100 (C), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/influxdata)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 68/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 61/100 (C)
- Developer Experience: 100/100 (A+)
- Agent Discovery: 100/100 (A+)
- Agent Understanding: 40/100 (F)
- Agent Usability: 72/100 (B)

## Check Results

### API Design

- [warn] Schema coverage & depth — 10/15 (67%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 78%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.influxdata.com/influxdb-signup/; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 9/9 operations carry a description. Investigated: sdk 100%.
- [skip] Quickstart present — No surface produced evidence for this capability in this run.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — llms-full.txt reachable at https://influxdata.com/llms-full.txt. Investigated: docs 100%, sdk 0%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/influxdata, 77435 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [pass] Crawlable / AEO — Sitemap with 100% lastmod coverage; newest entry < 90 days old. Investigated: wellknown 100%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Docs structured data — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

InfluxData's API program shows meaningful strength in overall usability and schema quality, but two areas are creating friction that will slow partner adoption and block AI-agent integrations: the absence of machine-readable agent context (no AGENTS.md) means coding agents cannot self-orient and will hallucinate integration patterns, and gaps in security governance hygiene make it harder for partners to validate safe usage before committing. Prioritize publishing an agent instructions file and tightening auth/security signals first, then close the runnable-collection gap so partners and their agents can validate real workflows end-to-end without hand-holding.