Drippay Runs API

Start, update, and inspect agent runs.

Operations 8

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /v1/runs Start tracking a new agent run · Start a new agent run #
Ask an LLM
“How do I begin tracking an agent run for a customer's workflow?”
“What status does a new run start in before any events arrive?”
Tell an agent
Start a new run of workflow {workflowId} for customer {customerId}.
Open a run for customer {customerId} on workflow {workflowId} as a child of run {parentRunId}.
GET /v1/runs List agent runs with filters · List runs #
Ask an LLM
“Which agent runs has a given customer had this week?”
“Can I filter my agent runs by workflow and status?”
Tell an agent
List agent runs for customer {customerId}.
Show the last {limit} runs of workflow {workflowId} with status {status}.
PATCH /v1/runs/{id} Update a run's status or end it · Update or end a run #
Ask an LLM
“How do I mark an agent run as completed or failed?”
“Is the duration computed automatically when a run ends?”
Tell an agent
End run {id} as completed.
Mark run {id} as failed.
GET /v1/runs/{id} Get a run's metadata and summary totals · Get run details #
Ask an LLM
“What are the summary totals for one specific agent run?”
“Can I look up a single run's status and metadata by its ID?”
Tell an agent
Get the details and totals for run {id}.
Show me the status of run {id}.
GET /v1/runs/{id}/timeline Get a run's full event timeline for debugging · Get run timeline #
Ask an LLM
“What exactly happened step by step during an agent run?”
“Can I see retry chains and anomalies detected in a run's events?”
Tell an agent
Show the event timeline for run {id} with includeAnomalies set to {includeAnomalies}.
Page through run {id}'s timeline from cursor {cursor}, {limit} events at a time.
POST /v1/run-events Emit a single event to a run (legacy) · Emit an event to a run (legacy) #
Ask an LLM
“How do I send one usage event to a run through the legacy run-events endpoint?”
“Does the older single run-event call create a charge or only record it for debugging?”
Tell an agent
Emit one event to a run using the legacy single run-event endpoint.
Record a single idempotent step event on my agent run for debugging.
POST /v1/run-events/batch Emit a batch of events to runs (legacy) · Batch emit events to runs (legacy) #
Ask an LLM
“Can I send many run events in one request with the legacy batch endpoint?”
“What happens to a batched event that has no run ID attached?”
Tell an agent
Send this batch of events to their runs in one legacy batch call.
Batch-emit these events, each with its own run, customer and workflow.
POST /v1/runs/record Record a complete run in one call · Record a complete run in one call #
Ask an LLM
“Is there a single call that starts a run, adds its events and ends it?”
“Will a workflow be auto-created if I record a run with a new slug?”
Tell an agent
Record a finished run of workflow {workflow} for customer {customerId} with status {status}.
Record a failed run of {workflow} for customer {customerId} with status {status} and error {errorMessage}.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/drippay:drippay-runs-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

drippay-runs-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Drip Runs API
  description: '# Drip API


    **Usage-based billing + execution ledger.**


    ---


    ## 60-Second Quickstart (Core SDK)


    ### 1.'
  version: 1.0.0
  contact:
    name: Drip Support
    email: support@drippay.dev
  x-logo:
    url: https://drippay.dev/logo.svg
    altText: Drip
servers:
- url: https://api.drippay.dev
  description: Production
- url: http://localhost:3001
  description: Development
security:
- bearerAuth: []
tags:


# --- truncated at 32 KB (47 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/drippay/refs/heads/main/openapi/drippay-runs-api-openapi.yml