# Midjourney — API Agent Score

> Score: 53/100 (Grade: D) | Domain: midjourney.com | Rubric: 1.0.0 | Checked: July 24, 2026

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

[View full report](https://www.postman.com/ai/ai-ready-apis/company/midjourney)
[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: 75/100 (B)
- Developer Experience: 40/100 (F)
- Agent Discovery: 59/100 (D)
- Agent Understanding: 55/100 (D)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [pass] Schema coverage & depth — 30/30 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%.
- [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

- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Description completeness — 15/15 operations lack a description. Investigated: sdk 0%.
- [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 (websites/midjourney_hc_en-us, 1257 snippets). Investigated: docs 100%, sdk 100%, cli 0%, mcp 0%, wellknown 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.
- [warn] Docs reachable, not hard auth-gated — All 50 sampled pages require authentication. Investigated: docs 20%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://docs.midjourney.com/llms.txt, https://docs.midjourney.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No sampled pages support .md URLs (0/50 tested). Investigated: docs 57%.
- [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] Docs structured data — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 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%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [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

Midjourney's API program shows real strength in its underlying API surface, but partners and their AI agents face significant friction at every stage of discovery, onboarding, and integration. The two most critical gaps are a missing self-service developer portal — meaning partners cannot evaluate or onboard without a sales conversation — and an absence of the machine-readable signals (llms.txt, AGENTS.md, idempotency documentation, runnable collections) that AI coding agents need to integrate reliably. Closing these gaps should be the immediate priority to unlock self-serve partner growth and make the API safe for agent-driven workflows.