Argilla
Argilla is an open-source data annotation and curation platform designed for AI engineers and domain experts building high-quality datasets for LLMs and NLP models. The platform provides a FastAPI-based REST API for managing workspaces, datasets, records, responses, suggestions, and vectors, enabling RLHF and preference tuning pipelines. Developers interact with Argilla through a Python SDK (pip install argilla) or directly via REST using API key authentication. Argilla supports deployment on Hugging Face Spaces, Docker, and self-hosted environments, and is licensed under Apache-2.0. The platform recently joined Hugging Face, deepening its integration with the broader open ML ecosystem.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Argilla the way a machine reads it — 37 machine-readable artifacts across 15 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 — Argilla scores 48.9/100 (developing), with a separate agent-readiness read of 48/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Argilla
Each block below is one kind of artifact we hold for Argilla. 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 15
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.
Argilla Authentication API
The Authentication API from Argilla — 4 operation(s) for authentication.
Argilla datasets API
The datasets API from Argilla — 19 operation(s) for datasets.
Argilla fields API
The fields API from Argilla — 1 operation(s) for fields.
Argilla info API
The info API from Argilla — 2 operation(s) for info.
Argilla jobs API
The jobs API from Argilla — 1 operation(s) for jobs.
Argilla metadata properties API
The metadata properties API from Argilla — 2 operation(s) for metadata properties.
Argilla questions API
The questions API from Argilla — 1 operation(s) for questions.
Argilla records API
The records API from Argilla — 3 operation(s) for records.
Argilla responses API
The responses API from Argilla — 2 operation(s) for responses.
Argilla settings API
The settings API from Argilla — 1 operation(s) for settings.
Argilla suggestions API
The suggestions API from Argilla — 1 operation(s) for suggestions.
Argilla users API
The users API from Argilla — 4 operation(s) for users.
Argilla vectors-settings API
The vectors-settings API from Argilla — 1 operation(s) for vectors-settings.
Argilla webhooks API
The webhooks API from Argilla — 3 operation(s) for webhooks.
Argilla workspaces API
The workspaces API from Argilla — 5 operation(s) for workspaces.
Scroll within the panel for all 15 ·
Pricing 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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate 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.
Argilla Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Argilla Finops
FINOPSSemantic 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.
Argilla 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.
Argilla API Rules
SPECTRALJSON Schema 11
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.
Dataset
JSON SCHEMAField
JSON SCHEMAMetadataProperty
JSON SCHEMAQuestion
JSON SCHEMARecord
JSON SCHEMAResponse
JSON SCHEMASuggestion
JSON SCHEMAUser
JSON SCHEMAVectorSettings
JSON SCHEMAWebhook
JSON SCHEMAWorkspace
JSON SCHEMAScroll within the panel for all 11 ·
Examples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Argilla Add Records Example
EXAMPLESecurity 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.
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 Argilla — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/argilla · machine-readable index on apis.io