Val Town
Val Town is a social coding platform where JavaScript and TypeScript programs called "vals" run instantly as HTTP endpoints, scheduled cron jobs, or email handlers without any infrastructure setup. It targets developers who want to write and deploy small server-side scripts and APIs directly in the browser. Val Town exposes a versioned REST API (v1, v2, v3) at api.val.town covering vals management, blob storage, SQLite databases, email sending, telemetry, and OAuth connections to third-party services. A TypeScript SDK (@valtown/sdk) is autogenerated from the published OpenAPI spec, and a hosted MCP server enables LLM-native integrations.
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 Val Town the way a machine reads it — 32 machine-readable artifacts across 13 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 — Val Town scores 52.7/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 Val Town
Each block below is one kind of artifact we hold for Val Town. 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 13
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.
Val Town TypeScript SDK
Official TypeScript and JavaScript client library for the Val Town REST API, autogenerated from the OpenAPI spec via Stainless. Published as @valtown/sdk on npm and supports Nod...
Val Town MCP Server
Model Context Protocol server hosted by Val Town at api.val.town/v3/mcp enabling LLMs and AI agents to interact with Val Town resources and run vals programmatically via HTTP tr...
Val Town alias API
Many API endpoints accept IDs instead of user-facing names. The alias endpoints let you convert between the user-facing name of a val or another object into an ID that can be us...
Val Town blobs API
Blobs
Val Town connections API
The connections API from Val Town — 2 operation(s) for connections.
Val Town emails API
Emails
Val Town files API
The files API from Val Town — 1 operation(s) for files.
Val Town me API
These endpoints give access to details and data from the requesting user.
Val Town orgs API
The orgs API from Val Town — 2 operation(s) for orgs.
Val Town sqlite API
SQLite
Val Town telemetry API
The telemetry API from Val Town — 2 operation(s) for telemetry.
Val Town users API
Users
Val Town vals API
These endpoints let you get, create, and run vals.
Scroll within the panel for all 13 ·
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.
Val Town 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.
Val Town 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.
Val Town 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.
Val Town API Rules
SPECTRALJSON Schema 7
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.
Branch
JSON SCHEMAMembership
JSON SCHEMAOrg
JSON SCHEMAResultSet
JSON SCHEMATEnvironmentVariable
JSON SCHEMAUser
JSON SCHEMAVal
JSON SCHEMAScroll within the panel for all 7 ·
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.
Val Town Get User Example
EXAMPLEVal Town List Vals Example
EXAMPLEVal Town Send Email Example
EXAMPLESecurity Posture 3
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 Val Town — 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
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
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 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/val-town · machine-readable index on apis.io