RevRule by Payload

RevRule by Payload provides a revenue‑sharing platform that turns agreements and revenue streams into auditable economic entitlements. Users upload agreements, connect revenue sources, and the system calculates who is owed what. Payments are facilitated via a two‑path x402 USDC endpoint on Base, requiring a 0.01 USDC payment per event. The API supports submitting revenue events, retrieving entitlement calculations, and managing payment transactions, enabling businesses to automate revenue distribution and maintain transparent ledgers.

RevRule by Payload is listed with 1 API on the APIs.io network. Tagged areas include Company, Revenue, Payments, and Fintech.

The RevRule by Payload catalog on APIs.io includes 1 Spectral governance ruleset.

RevRule by Payload’s developer surface includes documentation, authentication, API reference, and 6 more developer resources.

📡 Profile data on GitHub

10.9/100 minimal ▬ flat Agent 5/100 human only Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API

Company Revenue Payments Fintech

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 10.9/100 · minimal

Contract Quality 0.0 / 21

Developer Ergonomics 3.4 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 4.6 / 9

Regulatory Posture 2.3 / 15

Agent readiness — 5/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments 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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/revrule/"><img src="https://apis.io/badge/revrule/card.svg" alt="RevRule by Payload 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):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
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)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 0.0 — up to +20.0 composite points
Developer Ergonomics scores 20.2 — up to +16.0 composite points

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.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/revrule/apis.yml: open an issue on github.com/api-evangelist/revrule to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

RevRule API

RevRule by Payload provides a revenue‑sharing platform with x402 USDC payment endpoints.

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

RevRule by Payload API Rules

12 rules · 10 errors 1 warnings 1 info

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Revrule Authentication

apiKey · 1 scheme

SECURITY

Revrule Domain Security

TLSv1.3

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Revrule Agentic Access

3 operations · 2 acting

AGENTIC

Resources

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Spectral

Spectral

ErrorCatalog

ErrorCatalog

Conformance

Conformance

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Other 1

Properties that don't map to a standard resource type

Hosts

Hosts

Source (apis.yml)

aid: revrule
name: RevRule by Payload
description: RevRule by Payload provides a revenue‑sharing platform that turns agreements and revenue streams into auditable
  economic entitlements. Users upload agreements, connect revenue sources, and the system calculates who is owed what. Payments
  are facilitated via a two‑path x402 USDC endpoint on Base, requiring a 0.01 USDC payment per event. The API supports submitting
  revenue events, retrieving entitlement calculations, and managing payment transactions, enabling businesses to automate
  revenue distribution and maintain transparent ledgers.
url: https://raw.githubusercontent.com/api-evangelist/revrule/refs/heads/main/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-14 (modular-v1; was harvest)
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: none
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.20'
created: '2026-10-14'
modified: '2026-10-14'
tags:
- Company
- Revenue
- Payments
- Fintech
tags_raw:
- Company
- Revenue
- Payments
- API
- FinTech
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: AgenticAccess
  url: agentic-access/revrule-agentic-access.yml
- type: Spectral
  url: rules/revrule-rules.yml
- type: ErrorCatalog
  url: errors/revrule-problem-types.yml
- type: Conformance
  url: conformance/revrule-conformance.yml
- type: Hosts
  url: hosts/revrule-hosts.yml
- type: Documentation
  url: https://developers.dev/openapi.json/
- type: Authentication
  url: authentication/revrule-authentication.yml
- type: DomainSecurity
  url: security/revrule-domain-security.yml
- type: APIReference
  url: https://payload-rail.fly.dev/openapi.json
apis:
- name: RevRule API
  description: RevRule by Payload provides a revenue‑sharing platform with x402 USDC payment endpoints.
  humanURL: https://payload-rail.fly.dev
  baseURL: https://payload-rail.fly.dev
  aid: revrule:revrule-api
x-submission-notes: 'Two-path x402 USDC endpoint on fly.dev, no site, gmail contact — crypto rails for an unknown entity;
  ''payload'' slug is a different listed provider | Kin approved listing 2026-10-14 (case-by-case: Two-path x402 USDC endpoint
  on fly.dev, no site, gmail contact — crypto rails for an unknown entity; ''payload'' slug is a)'
x-submission-probe: openapi.json 200 (2 paths, x402 on Base); root 404
x-submitted-by: kyler.simmons.partners@gmail.com (apis.io/add, 2026-10-13)
x-coverage:
  state: none
  reason: no-developer-program
  method: derived
  generated: '2026-10-14'
  generator: derive-coverage.py (pre-flight evidence)
  detail: the company publishes no developer documentation host and no machine-readable contract on its own domain
  evidence:
  - url: https://payload-rail.fly.dev/openapi.json
    status: 200
x-enrichment:
  date: '2026-10-14'
  status: enriched
  artifacts_added: 9
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

RevRule by Payload API — frequently asked questions

Does RevRule by Payload have an API?

Yes. APIs.io lists 1 API from RevRule by Payload, including RevRule API.

How do I authenticate with the RevRule by Payload API?

RevRule by Payload uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Revrule Authentication.

Is the RevRule by Payload API ready for AI agents?

RevRule by Payload has a Kin Score of 10.9 out of 100 (minimal) and an Agent Readiness score of 5.0 (human-only), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/revrule"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/revrule/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/revrule/evidence"

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.

GitHub Google LinkedIn

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