Currents (Currents Software Inc., currents.dev) is a Playwright-focused test reporter, cloud dashboard and test orchestrator that helps teams scale Playwright tests in CI and optimize complex test suites for health, reliability and performance. It also supports Cypress and other frameworks, and offers a REST API, the @currents/cmd command line tool, a trace API, an MCP server for AI agents, and integrations with GitHub, GitLab, Bitbucket, Jira, Linear, Slack and Microsoft Teams.
Currents publishes 25 API contracts indexed on the APIs.io network, including Actions API, Animation API, Animations API, and 22 more. Tagged areas include Company, Testing, Playwright, Test Automation, and CI/CD.
The Currents catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.
Currents’ developer surface includes CLI, changelog, authentication, documentation, API reference, getting-started guide, support, and 50 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/currents-dev/"><img src="https://apis.io/badge/currents-dev/card.svg" alt="Currents on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Agentic Commerce Well-Known Document+5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's Ask about this →
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
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.
Manage test actions (rules) that automatically modify test behavior. Actions allow you to: - **Skip** tests that match certain conditions - **Quarantine** flaky tests so their f...
Retrieve structured test failure context for AI debugging. The Context endpoint provides test failure data in JSON or Markdown format, suitable for feeding into AI tools and MCP...
Query and filter errors from the Error Explorer. Returns aggregated error metrics for a project within a date range, with optional filters for error target, message, category, a...
Query spec file execution instances. An instance represents a single spec file execution within a run. It contains detailed information about test results, duration, and machine...
The organizations the authenticated user belongs to. Answers for the person an OAuth access token or personal access token was issued to, not for the organization. Organization ...
Manage and query projects in your organization. Projects are the top-level containers for test runs, specs, and test results. Each project has a unique project ID and can be con...
Query and manage test runs. A run represents a single execution of your test suite. Runs contain spec files which are executed across multiple instances. You can query run detai...
Browser sessions an agent recorded: a title, how it ended, the git commit and pull request, and attachments such as a trace, screenshots and a video. A session is not a run. It ...
Generate test signatures. Test signatures are unique identifiers for tests based on project, spec file path, and test title. They are used to track tests across multiple runs.
Query spec file metrics and statistics. Get aggregated metrics for spec files within a project, including execution counts, failure rates, flakiness rates, and duration statistics.
Query historical test execution results. Test results provide detailed information about individual test executions across multiple runs. You can filter by date range, branch, t...
Explore and analyze test metrics. The Tests Explorer provides aggregated metrics for tests within a project, including execution counts, failure rates, flakiness rates, and dura...
Manage HTTP webhooks for projects. Webhooks allow you to receive HTTP POST notifications when certain events occur in your test runs: - **RUN_FINISH**: Run completed (passed or ...
Official Currents MCP server giving AI agents Currents CI test results (runs, failures, traces, analytics), actions, webhooks, Jira issues, sessions and share links. Hosted at h...
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
aid: currents-dev
name: Currents
description: Currents (Currents Software Inc., currents.dev) is a Playwright-focused test reporter, cloud dashboard and test
orchestrator that helps teams scale Playwright tests in CI and optimize complex test suites for health, reliability and
performance. It also supports Cypress and other frameworks, and offers a REST API, the @currents/cmd command line tool,
a trace API, an MCP server for AI agents, and integrations with GitHub, GitLab, Bitbucket, Jira, Linear, Slack and Microsoft
Teams.
url: https://artifacts.apis.io/currents-dev/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-04 (modular-v1; was harvest)
accessModel:
pricing: paid
onboarding: unknown
trial: false
try_now: false
public: false
label: Paid
confidence: high
probe_state: covered
source:
- plans
- authentication
- scopes
- rate-limits
- security
generated: '2026-11-13'
method: derived
specificationVersion: '0.20'
created: '2026-11-04'
modified: '2026-11-04'
tags:
- Company
- Testing
- Playwright
- Test Automation
- CI/CD
- Test Orchestration
- Developer Tools
- MCP
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
image: https://currents.dev/img/og-card-v3.jpg
common:
- type: AgenticAccess
url: agentic-access/currents-dev-agentic-access.yml
- type: RateLimits
url: rate-limits/currents-dev-rate-limits.yml
- type: Plans
url: plans/currents-dev-plans-pricing.yml
- type: Spectral
url: rules/currents-dev-rules.yml
- type: JSONLD
url: json-ld/currents-dev-context.jsonld
- type: Vocabulary
url: vocabulary/currents-dev-vocabulary.yml
- type: AgentSkill
url: skills/_index.yml
- type: Webhooks
url: asyncapi/currents-dev-webhooks.yml
- type: DataModel
url: data-model/currents-dev-data-model.yml
- type: CLI
url: cli/currents-dev-cli.yml
- type: ChangeLog
url: changelog/currents-dev-changelog.yml
- type: Conventions
url: conventions/currents-dev-conventions.yml
- type: Compliance
url: https://currents.dev/security
- type: Deprecation
url: lifecycle/currents-dev-lifecycle.yml
- type: Lifecycle
url: lifecycle/currents-dev-lifecycle.yml
- type: ErrorCatalog
url: errors/currents-dev-problem-types.yml
- type: Conformance
url: conformance/currents-dev-conformance.yml
- type: Overlay
url: overlays/currents-dev-mcp-overlay.yaml
- type: LLMsTxt
url: llms/currents-dev-llms.txt
- type: ToolCrosswalk
url: mcp/currents-dev-tool-crosswalk.yml
- type: MCPServer
url: mcp/currents-dev-mcp.yml
- type: SecurityTxt
url: well-known/currents-dev-security.txt
- type: WellKnown
url: well-known/currents-dev-well-known.yml
- type: Hosts
url: hosts/currents-dev-hosts.yml
- type: IntegrationEdges
url: integrations/currents-dev-integration-edges.yml
- type: Vendors
url: vendors/currents-dev-vendors.yml
- type: SDKs
url: packages/currents-dev-packages.yml
- type: Packages
url: packages/currents-dev-packages.yml
- type: DeveloperPortal
url: https://docs.currents.dev\
- type: Authentication
url: authentication/currents-dev-authentication.yml
- type: OAuthScopes
url: scopes/currents-dev-scopes.yml
- type: TrustCenter
url: security/currents-dev-trust-center.yml
- type: VulnerabilityDisclosure
url: security/currents-dev-vulnerability-disclosure.yml
- type: DomainSecurity
url: security/currents-dev-domain-security.yml
- type: Website
url: https://currents.dev/
- type: Documentation
url: https://docs.currents.dev
- type: APIReference
url: https://docs.currents.dev/api
- type: GettingStarted
url: https://docs.currents.dev/getting-started/your-first-playwright-run
- type: Support
url: https://docs.currents.dev/resources/support
- type: Blog
url: https://currents.dev/blog
- type: ChangeLog
url: https://currents.dev/changelog
- type: GitHubOrganization
url: https://github.com/currents-dev
- type: Pricing
url: https://currents.dev/pricing
- type: SignUp
url: https://app.currents.dev/signup
- type: TermsOfService
url: https://currents.dev/tos
- type: PrivacyPolicy
url: https://currents.dev/privacy-policy
- type: Security
url: https://currents.dev/security
- type: StatusPage
url: https://currents.instatus.com/
- type: LlmsTxt
url: https://docs.currents.dev/llms.txt
- type: Contact
url: https://currents.dev/contact
- type: X
url: https://x.com/currents_dev
- type: UsageTerms
url: terms/currents-dev-terms-of-service.yml
- type: DataProcessing
url: privacy/currents-dev-privacy-policy.yml
- type: Attestations
url: compliance/currents-dev-compliance.yml
- type: Eligibility
url: eligibility/currents-dev-eligibility.yml
- type: AIPreferences
url: ai-preferences/currents-dev-ai-preferences.yml
- type: DataLicense
url: data-license/currents-dev-data-license.yml
apis:
- aid: currents-dev:currents-dev-actions-api
name: Currents Actions API
description: 'Manage test actions (rules) that automatically modify test behavior.
Actions allow you to:
- **Skip** tests that match certain conditions
- **Quarantine** flaky tests so their failures don''t fail the run
- **Tag** tests with custom labels for organization
Each action has a **matcher** that defines which tests it applies to,
based on conditions like test title, file path, tags, git branch, etc.'
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Actions
properties:
- type: OpenAPI
url: openapi/currents-dev-actions-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- type: JSONSchema
url: json-schema/currents-dev-affected-tests-list-response-schema.json
- type: JSONSchema
url: json-schema/currents-dev-create-action-request-schema.json
- type: JSONSchema
url: json-schema/currents-dev-affected-test-executions-response-schema.json
- type: JSONSchema
url: json-schema/currents-dev-update-action-request-schema.json
- type: JSONSchema
url: json-schema/currents-dev-action-delete-response-schema.json
- type: JSONSchema
url: json-schema/currents-dev-actions-list-response-schema.json
- aid: currents-dev:currents-dev-animation-api
name: Currents Animation API
description: The Animation API from Currents — 1 operation(s) for animation.
humanURL: https://docs.currents.dev/api
baseURL: https://t.crts.sh
tags:
- Animation
properties:
- type: OpenAPI
url: openapi/currents-dev-animation-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-animations-api
name: Currents Animations API
description: The Animations API from Currents — 1 operation(s) for animations.
humanURL: https://docs.currents.dev/api
baseURL: https://t.crts.sh
tags:
- Animations
properties:
- type: OpenAPI
url: openapi/currents-dev-animations-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-attachments-api
name: Currents Attachments API
description: The Attachments API from Currents — 2 operation(s) for attachments.
humanURL: https://docs.currents.dev/api
baseURL: https://t.crts.sh
tags:
- Attachments
properties:
- type: OpenAPI
url: openapi/currents-dev-attachments-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-context-api
name: Currents Context API
description: 'Retrieve structured test failure context for AI debugging.
The Context endpoint provides test failure data in JSON or Markdown format, suitable for feeding into AI tools and MCP
integrations. It supports three detail levels:
- **Run-level**: Summary of all failures across a run
- **Instance-level**: Failures within a single spec file
- **Test-level**: Full detail for a single test attempt'
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Context
properties:
- type: OpenAPI
url: openapi/currents-dev-context-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- type: JSONSchema
url: json-schema/currents-dev-context-response-schema.json
- aid: currents-dev:currents-dev-currents-trace-api-api
name: Currents Currents Trace API
description: The Currents Trace API API from Currents — 1 operation(s) for currents trace api.
humanURL: https://docs.currents.dev/api
baseURL: https://t.crts.sh
tags:
- Currents Trace API
properties:
- type: OpenAPI
url: openapi/currents-dev-currents-trace-api-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-digest-api
name: Currents Digest API
description: The Digest API from Currents — 1 operation(s) for digest.
humanURL: https://docs.currents.dev/api
baseURL: https://t.crts.sh
tags:
- Digest
properties:
- type: OpenAPI
url: openapi/currents-dev-digest-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-download-api
name: Currents Download API
description: The Download API from Currents — 1 operation(s) for download.
humanURL: https://docs.currents.dev/api
baseURL: https://t.crts.sh
tags:
- Downloads
tags_raw:
- Download
properties:
- type: OpenAPI
url: openapi/currents-dev-download-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-errors-explorer-api
name: Currents Errors Explorer API
description: 'Query and filter errors from the Error Explorer.
Returns aggregated error metrics for a project within a date range, with optional filters
for error target, message, category, action, tags, branches, authors, and groups.'
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Errors Explorer
properties:
- type: OpenAPI
url: openapi/currents-dev-errors-explorer-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- type: JSONSchema
url: json-schema/currents-dev-errors-explorer-response-schema.json
- aid: currents-dev:currents-dev-filmstrip-api
name: Currents Filmstrip API
description: The Filmstrip API from Currents — 1 operation(s) for filmstrip.
humanURL: https://docs.currents.dev/api
baseURL: https://t.crts.sh
tags:
- Filmstrip
properties:
- type: OpenAPI
url: openapi/currents-dev-filmstrip-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-frames-api
name: Currents Frames API
description: The Frames API from Currents — 3 operation(s) for frames.
humanURL: https://docs.currents.dev/api
baseURL: https://t.crts.sh
tags:
- Frames
properties:
- type: OpenAPI
url: openapi/currents-dev-frames-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-instances-api
name: Currents Instances API
description: 'Query spec file execution instances.
An instance represents a single spec file execution within a run. It contains
detailed information about test results, duration, and machine that executed
the spec file.'
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Instances
properties:
- type: OpenAPI
url: openapi/currents-dev-instances-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- type: JSONSchema
url: json-schema/currents-dev-instance-response-schema.json
- aid: currents-dev:currents-dev-integrations-api
name: Currents Integrations API
description: Manage third-party integrations such as Jira.
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Integration
tags_raw:
- Integrations
properties:
- type: OpenAPI
url: openapi/currents-dev-integrations-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: JSONSchema
url: json-schema/currents-dev-link-jira-issue-from-run-test-request-schema.json
- type: JSONSchema
url: json-schema/currents-dev-create-jira-issue-from-run-test-request-schema.json
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-organizations-api
name: Currents Organizations API
description: 'The organizations the authenticated user belongs to.
Answers for the person an OAuth access token or personal access token was issued to, not for the organization. Organization
API keys identify no user and are refused.'
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Organization
tags_raw:
- Organizations
properties:
- type: OpenAPI
url: openapi/currents-dev-organizations-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- type: JSONSchema
url: json-schema/currents-dev-my-organizations-response-schema.json
- aid: currents-dev:currents-dev-projects-api
name: Currents Projects API
description: 'Manage and query projects in your organization.
Projects are the top-level containers for test runs, specs, and test results.
Each project has a unique project ID and can be configured with various settings.'
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Project
tags_raw:
- Projects
properties:
- type: OpenAPI
url: openapi/currents-dev-projects-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: JSONSchema
url: json-schema/currents-dev-project-insights-response-schema.json
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-requests-api
name: Currents Requests API
description: The Requests API from Currents — 4 operation(s) for requests.
humanURL: https://docs.currents.dev/api
baseURL: https://t.crts.sh
tags:
- Requests
properties:
- type: OpenAPI
url: openapi/currents-dev-requests-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-runs-api
name: Currents Runs API
description: 'Query and manage test runs.
A run represents a single execution of your test suite. Runs contain spec files
which are executed across multiple instances. You can query run details, cancel
runs, reset failed specs, and delete runs.
Per-test outcome counters on specs (`results.stats`) use the `RecordedTestOutcome` vocabulary—see **components/schemas**
for how **pending** and **skipped** differ from **failures**.'
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Runs
properties:
- type: OpenAPI
url: openapi/currents-dev-runs-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: JSONSchema
url: json-schema/currents-dev-create-run-context-links-response-schema.json
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-sessions-api
name: Currents Sessions API
description: 'Browser sessions an agent recorded: a title, how it ended, the git commit and pull request, and attachments
such as a trace, screenshots and a video.
A session is not a run. It does not appear in run lists or in analytics, and it has no spec files or tests. Share one
with `POST /share` and `sessionId`.'
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Sessions
properties:
- type: OpenAPI
url: openapi/currents-dev-sessions-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: JSONSchema
url: json-schema/currents-dev-create-session-request-schema.json
- type: JSONSchema
url: json-schema/currents-dev-session-list-item-schema.json
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-signature-api
name: Currents Signature API
description: 'Generate test signatures.
Test signatures are unique identifiers for tests based on project, spec file path,
and test title. They are used to track tests across multiple runs.'
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Signature
properties:
- type: OpenAPI
url: openapi/currents-dev-signature-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- type: JSONSchema
url: json-schema/currents-dev-test-signature-request-schema.json
- type: JSONSchema
url: json-schema/currents-dev-test-signature-response-schema.json
- aid: currents-dev:currents-dev-snapshots-api
name: Currents Snapshots API
description: The Snapshots API from Currents — 3 operation(s) for snapshots.
humanURL: https://docs.currents.dev/api
baseURL: https://t.crts.sh
tags:
- Snapshots
properties:
- type: OpenAPI
url: openapi/currents-dev-snapshots-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- aid: currents-dev:currents-dev-spec-files-api
name: Currents Spec Files API
description: 'Query spec file metrics and statistics.
Get aggregated metrics for spec files within a project, including execution counts,
failure rates, flakiness rates, and duration statistics.'
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Spec Files
properties:
- type: OpenAPI
url: openapi/currents-dev-spec-files-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- type: JSONSchema
url: json-schema/currents-dev-metrics-summary-schema.json
- type: JSONSchema
url: json-schema/currents-dev-spec-files-response-schema.json
- aid: currents-dev:currents-dev-test-results-api
name: Currents Test Results API
description: 'Query historical test execution results.
Test results provide detailed information about individual test executions
across multiple runs. You can filter by date range, branch, tags, git author,
and outcome (`status[]` values use the `RecordedTestOutcome` schema).'
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Test Results
properties:
- type: OpenAPI
url: openapi/currents-dev-test-results-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- type: JSONSchema
url: json-schema/currents-dev-test-results-response-schema.json
- aid: currents-dev:currents-dev-tests-api
name: Currents Tests API
description: The Tests API from Currents — 1 operation(s) for tests.
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Tests
properties:
- type: OpenAPI
url: openapi/currents-dev-tests-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- type: JSONSchema
url: json-schema/currents-dev-metrics-summary-schema.json
- aid: currents-dev:currents-dev-tests-explorer-api
name: Currents Tests Explorer API
description: 'Explore and analyze test metrics.
The Tests Explorer provides aggregated metrics for tests within a project,
including execution counts, failure rates, flakiness rates, and duration statistics.
Outcome strings are defined in the `RecordedTestOutcome` schema (see **components/schemas**). That schema explains how
each value maps to `metrics` on `GET /tests/{projectId}` (`ignored`, `failures`, etc.).
Narrative context for the dashboard is here:
[Test result statuses — Tests Explorer & REST API](https://docs.currents.dev/dashboard/tests/test-status).'
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Tests Explorer
properties:
- type: OpenAPI
url: openapi/currents-dev-tests-explorer-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- type: JSONSchema
url: json-schema/currents-dev-tests-explorer-response-schema.json
- aid: currents-dev:currents-dev-webhooks-api
name: Currents Webhooks API
description: 'Manage HTTP webhooks for projects.
Webhooks allow you to receive HTTP POST notifications when certain events occur in your test runs:
- **RUN_FINISH**: Run completed (passed or failed)
- **RUN_START**: Run started
- **RUN_TIMEOUT**: Run timed out
- **RUN_CANCELED**: Run was cancelled
Webhooks are useful for integrating with external tools like n8n, Zapier, or custom automation platforms.'
humanURL: https://docs.currents.dev/api
baseURL: https://api.currents.dev/v1
tags:
- Webhook
tags_raw:
- Webhooks
properties:
- type: OpenAPI
url: openapi/currents-dev-webhooks-api-openapi.yml
- type: Documentation
url: https://docs.currents.dev/api
- type: Authentication
url: https://docs.currents.dev/api/get-started/authentication
- type: Documentation
url: https://t.crts.sh/docs
- type: JSONSchema
url: json-schema/currents-dev-update-webhook-request-schema.json
- type: JSONSchema
url: json-schema/currents-dev-create-webhook-request-schema.json
- type: JSONSchema
url: json-schema/currents-dev-webhook-delete-response-schema.json
- type: JSONSchema
url: json-schema/currents-dev-webhook-list-response-schema.json
- type: JSONSchema
url: json-schema/currents-dev-webhook-response-schema.json
x-coverage:
state: covered
reason: identity-verified
detail: Name, description, image and link pointers taken from currents.dev homepage (title, meta description, footer "Currents
Software Inc.") and its docs llms.txt; every pointer fetched with a browser UA on 2026-11-04.
evidence:
- url: https://currents.dev/
status: 200
- url: https://docs.currents.dev/api
status: 200
- url: https://docs.currents.dev/resources/support
status: 200
- url: https://currents.instatus.com/
status: 200
- url: https://app.currents.dev/signup
status: 200
- url: https://currents.dev/contact
status: 200
- url: https://docs.currents.dev/llms.txt
status: 200
- url: https://x.com/currents_dev
status: 200
x-enrichment:
date: '2026-11-04'
status: enriched
artifacts_added: 66
pass: modular-v1
engine: identity=anthropic,contract=anthropic,surfaces=anthropic,docs=anthropic,regulatory=anthropic
Currents API — frequently asked questions
Does Currents have an API?
Yes. APIs.io lists 25 APIs from Currents, including Currents Actions API, Currents Animation API and Currents Animations API, and 22 more.
Is there an OpenAPI specification for the Currents API?
Yes. APIs.io indexes 25 OpenAPI specifications for Currents, each linked for download from this page.
How do I authenticate with the Currents API?
Currents documents its authentication (apiKey/http/oauth2 · 3 schemes). The details are profiled on APIs.io as Currents Authentication.
How much does the Currents API cost?
Currents publishes its prices; its Scale plan is $49 as of 2026-11-04. APIs.io lists 3 pricing plans for Currents, with each plan's price, limits and inclusions under Pricing on this page.
Does Currents have an MCP server?
Yes. APIs.io lists 1 MCP server for Currents: Official Currents MCP server giving AI agents Currents CI test results (runs, failures, traces, analytics), actions, webhooks, Jira issues, sessions and share links. Hosted at https://mcp.currents.dev
Is the Currents API ready for AI agents?
Currents has a Kin Score of 77.7 out of 100 (exemplar) and an Agent Readiness score of 55.8 (agent-ready), scored by API Evangelist on 2026-11-13.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: