agent-cloud-terms / README.md
sigrid-hal9's picture
Upload folder using huggingface_hub
a9af9f4 verified
|
Raw History Blame Contribute Delete
4.12 kB
metadata
license: cc-by-4.0
language:
  - en
pretty_name: agent-cloud-terms
size_categories:
  - n<1K
tags:
  - cloud
  - ai-agents
  - agent-cloud
  - hosting
  - pricing
  - scale-to-zero
  - spend-cap

agent-cloud-terms

Eight terms for "clouds that AI agents use", each with a one-sentence definition and, per provider, what that provider's own docs say — quoted, sourced and dated. For agent builders, evaluator authors and writers who need a machine-readable, citable table.

Files

File What it is
terms.csv The eight terms, one row each: term, definition (the one-sentence definition used across the other pieces), agent_question (what an agent asks to check it).
providers.csv One row per term and provider: term, provider, handling (how the provider handles it, in plain words), quote (the exact sentence from the provider's docs), source_url, checked (date the quote was read).

Quick start

from datasets import load_dataset

# One config per CSV file (named after the file)
terms = load_dataset("hal9/agent-cloud-terms", "terms", split="train")
providers = load_dataset("hal9/agent-cloud-terms", "providers", split="train")

Or read the CSVs directly from the repository.

The eight terms

  1. agent-native cloud — a cloud an AI agent can sign up for, pay for and deploy to with no person in the loop.
  2. agent self-signup — an agent creating its own credential with no human signup step.
  3. spend cap — a hard ceiling the work stops at, unlike a budget alert, which only warns.
  4. prepaid compute — compute paid up front from a balance that cannot go below zero.
  5. child key — a delegated credential under a parent key, funded by transfer and capped by a limit.
  6. claim link — a single-use link that attaches something an agent created to a person's account later.
  7. scale to zero — running no instances (and charging no compute) while idle, then starting one on the next request.
  8. persistent vs ephemeral storage — whether files survive a restart or redeploy.

Providers covered where their docs say something: Cloudish, Railway, Render, Fly.io, Vercel, Google Cloud Run, AWS, Heroku, Neon.

How it was built

On one date (see checked in each row), each provider's public documentation page named in source_url was read and the sentence that states the behaviour was copied verbatim into quote. The handling column restates it in plain words. "Agent-native cloud" is our own framing, not yet a standard term; the row for it is labelled accordingly.

Who made it

Written by Cloudish (cloudish.ai), by Hal9, which runs a cloud an AI agent deploys to. Cloudish chose the terms and appears as one provider among the others; rows where another provider does better are kept in, because the point is a fair table, not an ad.

Limits and biases

  • Cloudish chose the terms. The eight words are the vocabulary Cloudish uses to describe its category, not an industry-standard list.
  • Docs can differ from the product. Every row quotes documentation, checked on the date shown; a provider may have changed behaviour since.
  • Provider coverage is uneven. Some terms have many provider rows (scale to zero), others only the providers that document them (child key, prepaid compute — mostly Cloudish, because few others document those exact ideas).
  • "Agent-native cloud" is not vendor-neutral. It is explicitly marked as our framing.

Report a wrong row

Open a Discussion on this dataset page with the term, provider, and the corrected quote plus its URL and date. We update the row and bump the version tag.

License

The definitions, handling text and structure: CC BY 4.0. The quote column is a short quotation from each provider's own documentation for the purpose of comparison, with its source and date.

Citation

Cloudish (Hal9) (2026). agent-cloud-terms: eight agent-cloud terms with each provider's documented behaviour. Hugging Face dataset. Quotations checked 2026-11-16.