HUD
HUD (Human Union Data, Inc.) is a platform for building reinforcement-learning environments, tasks and benchmarks used to train and evaluate AI agents and models. Teams create environments with the open-source hud Python SDK and CLI or import Harbor tasks, run evaluations across frontier models, inspect traces, run automated QA agents that detect grader mistakes and reward hacking, train models on their own environments, and can list task data on DataVendor. The platform is exposed through a REST API at api.beta.hud.ai (routes under /v2, team API-key authentication).
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles HUD the way a machine reads it — 43 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — HUD scores 61.4/100 (strong), with a separate agent-readiness read of 58/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-31 · rubric v0.25.0
Put this on your own site. The badge is drawn live from HUD's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hud-ai/"
title="HUD on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hud-ai.svg"
alt="HUD Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/hud-ai/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/hud-ai/"
title="HUD on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/hud-ai/card.svg"
alt="HUD Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile HUD
Each block below is one kind of artifact we hold for HUD. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 24
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
HUD Builds API
The builds API from HUD — 16 operation(s) for builds.
HUD Byok Credentials API
The byok-credentials API from HUD — 2 operation(s) for byok-credentials.
HUD Checks API
The checks API from HUD — 4 operation(s) for checks.
HUD Completions API
The completions API from HUD — 1 operation(s) for completions.
HUD Data API
The data API from HUD — 7 operation(s) for data.
HUD Env Vars API
The env-vars API from HUD — 4 operation(s) for env-vars.
HUD Imports API
The imports API from HUD — 7 operation(s) for imports.
HUD Inference API
The inference API from HUD — 1 operation(s) for inference.
HUD Instances API
The instances API from HUD — 2 operation(s) for instances.
HUD Jobs API
The jobs API from HUD — 19 operation(s) for jobs.
HUD Limits API
The limits API from HUD — 3 operation(s) for limits.
HUD Member Secrets API
The member-secrets API from HUD — 2 operation(s) for member-secrets.
HUD Models API
The models API from HUD — 10 operation(s) for models.
HUD OAuth API
The oauth API from HUD — 1 operation(s) for oauth.
HUD Qa Agents API
The qa-agents API from HUD — 5 operation(s) for qa-agents.
HUD Qa API
The qa API from HUD — 3 operation(s) for qa.
HUD Registry API
The registry API from HUD — 4 operation(s) for registry.
HUD Rollouts API
The rollouts API from HUD — 6 operation(s) for rollouts.
HUD Storage API
The storage API from HUD — 3 operation(s) for storage.
HUD Tasks API
The tasks API from HUD — 9 operation(s) for tasks.
HUD Tasksets API
The tasksets API from HUD — 5 operation(s) for tasksets.
HUD Teams API
The teams API from HUD — 5 operation(s) for teams.
HUD Traces API
The traces API from HUD — 11 operation(s) for traces.
HUD Usage API
The usage API from HUD — 2 operation(s) for usage.
Scroll within the panel for all 24 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
HUD Platform MCP
Remote MCP server at api.beta.hud.ai over streamable HTTP requiring an API key; 8 tools listed.
MCP SERVERAgent Skills 4
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
hud-ai-diagnose-eval-run
AGENT SKILLhud-ai-explore-catalog
AGENT SKILLhud-environment-builder
AGENT SKILLhud-ai-run-qa-checks
AGENT SKILLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Hud Ai Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Hud Ai Rate Limits
RATE LIMITSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Hud Ai Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
HUD API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
BuildRegisterResponse
JSON SCHEMABuildResponse
JSON SCHEMAModelResponse
JSON SCHEMARegistryDetailResponse
JSON SCHEMATraceAnalysisContextResponse
JSON SCHEMATraceInfoResponse
JSON SCHEMASecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for HUD — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 6
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 10
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 10 ·
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/hud-ai · machine-readable index on apis.io
This is an independent, third-party profile of HUD, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.