# E.ON — API Agent Score

> Score: 53/100 (Grade: D) | Domain: eon.com | Rubric: 1.0.0 | Checked: October 5, 2026

E.ON scored 53/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 53/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 63/100 (C)
- Developer Experience: 47/100 (F)
- Agent Discovery: 55/100 (D)
- Agent Understanding: 51/100 (D)
- Agent Usability: 48/100 (F)

## Check Results

### API Design

- [pass] Security & governance hygiene — Code is formatter-clean with zero linter errors and zero style warnings. Investigated: sdk 100%, wellknown 100%.
- [warn] Schema coverage & depth — 0/88 (0%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 25%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%.
- [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

- [warn] Description completeness — 12/39 operations lack a description. Investigated: sdk 69%.
- [fail] Self-service developer portal — No self-service signup detected — no signup link on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved — so an agent can't onboard on its own. Investigated: docs 0%.
- [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] Registry & SDK presence — Indexed on Context7 (theochemui/eon, 722 snippets). Investigated: docs 100%, sdk 50%, cli 0%.
- [fail] llms.txt present, valid & comprehensive — No llms-full.txt was found at any candidate origin, so agents can't grab your full docs in one fetch. Investigated: docs 0%, sdk 0%.
- [fail] Crawlable / AEO — No sitemap found via robots.txt or /sitemap.xml on the docs host, so AI search engines have no crawl map for your docs. Investigated: wellknown 0%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [warn] Operation purpose clarity — Read/write classification is mostly ambiguous: only 10/39 operations classified. Investigated: sdk 63%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [fail] Machine-readable errors (RFC 9457) — No single common SDK base error class was found; errors do not share one root. Investigated: sdk 0%.
- [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

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [warn] Runnable collection with test scripts — README is present but has no runnable quickstart. Investigated: sdk 50%, platform 0%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 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

Eon's API program shows meaningful strength in core API design, but two areas are actively blocking partner momentum: partners cannot self-serve their way in (no signup path exists), and neither human developers nor AI agents can reliably discover, crawl, or consume your documentation. Fixing the partner front door — self-service access, machine-readable docs, and a crawlable sitemap — will have the largest immediate impact on partner activation, followed by closing error-handling and reliability gaps that stall integrations mid-build.