Prompt Driven
Prompt Driven (PDD) is the company behind Prompt-Driven Development, a prompt-native programming system in which .prompt files are the human-authored source language and traditional code (Python, TypeScript, Go, and others) is generated as an artifact. PDD ships as a single open-source Python CLI, pdd-cli, plus a local web interface, and offers agentic commands that implement GitHub issues automatically through a Define -> Generate -> Verify -> Test -> Update cycle. Positioned as "The Last Programming Language," the project is MIT-licensed, maintained by Greg Tanaka, and backed by 500 Global. It is a developer tool rather than a hosted API — there is no public REST/GraphQL API, OpenAPI spec, or MCP server; the developer surface is the CLI and its GitHub repository.
Prompt Driven is profiled on the APIs.io network. Tagged areas include Company, Developer Tools, Artificial Intelligence, Code Generation, and Developer Experience.
Prompt Driven’s developer surface includes documentation, support, CLI, changelog, and 14 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Agent Skills (SKILL.md packages) | undeclared | - | - | 2 |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 1
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 1
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 1
The organization behind the API
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.