Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Marketing / AffiliateRail API
AffiliateRail API logo

AffiliateRail API

51
AI ReadinessFoundational (C-)51/100
See full scorecard
Official vendor OpenAPI document · agent-readyMarketingMarketing Automationbearer151 EndpointsREST

For Agents

Create partners and tracking links, record clicks and sales, attribute and approve commissions, generate payouts, and recruit prospects. Authenticates with a bearer key.

Use for: I need to create a new affiliate partner in a program, Record a sale and attribute its commission, Approve a pending commission for a partner, Generate a payout batch for approved commissions

Not supported: Does not handle card payment processing, tax filing, or ad campaign buying. Use for affiliate program, partner, commission, and payout management only.

The AffiliateRail API runs an affiliate and partner program over one consistent REST contract, exposing every object in the product as an addressable resource. It creates partners, groups, tracking links, and coupons, records clicks, referrals, and sales, and attributes earnings through commission rules that can be approved, rejected, or added manually. Earnings flow into balances, payouts, and generated payout batches, while campaigns and sequences nurture partners and signed webhook endpoints stream events to your systems. A partner-finder surface adds prospect discovery, email reveal, notes, and a recruitment pipeline, and idempotency keys keep a retried write from recording the same action twice.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the AffiliateRail API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AffiliateRail API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faffiliaterail.com%2Faffiliaterail" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faffiliaterail.com%2Faffiliaterail" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AffiliateRail API.

Create and update partners, groups, and tracking links within a program

Record clicks, referrals, and sales and attribute earnings through commission rules

Approve, reject, or create manual commissions and read what matures between two dates

Generate payout batches, mark payouts paid, and read balances per partner

Register signed webhook endpoints, replay deliveries, and rotate signing secrets

Find and save prospect brands, reveal a prospect's email, and move prospects through a recruitment pipeline

Use Cases

Patterns agents use AffiliateRail API for, with concrete tasks.

★ Agent-Managed Affiliate Operations via Jentic

An AI agent can run the day-to-day of an affiliate program instead of a human clicking through a dashboard. Through Jentic the agent records a sale, lets commission rules attribute the earning, approves the commission once it is valid, and later generates a payout batch, each write carrying an idempotency key so a retry never double-counts.

Record a sale for a partner, approve the resulting commission once it is valid, and generate a payout batch for all approved commissions

Commission and Payout Lifecycle

AffiliateRail tracks earnings from attribution to payment. Commission rules compute earnings on sales in integer minor units with an explicit currency, commissions can be approved or rejected and queried for what matures between two dates, and balances roll up into payouts and generated payout batches that can be marked paid.

List the commissions maturing in a date range, then generate a payout batch and mark its payouts paid once settled

Partner Recruitment with Finder

The finder surface helps grow a program by sourcing new affiliates. An agent searches prospect brands, saves promising ones, reveals a prospect's email, adds notes, and moves prospects through pipeline stages and lanes, with credit balances tracking email reveals so recruitment stays within budget.

Search finder prospects for matching brands, save the best ones, reveal a prospect's email, and move it to the next pipeline stage

Key Endpoints

151 endpoints — the affiliaterail api runs an affiliate and partner program over one consistent rest contract, exposing every object in the product as an addressable resource.

METHOD

PATH

DESCRIPTION

GET

/v1/partners

List partners

POST

/v1/partners

Create a partner

GET

/v1/commissions

List commissions

POST

/v1/commissions/{id}/approve

Approve a commission

GET

/v1/sales

List sales

POST

/v1/payout_batches

Generate a payout batch

GET

/v1/links

List links

GET

/v1/partners

List partners

POST

/v1/partners

Create a partner

GET

/v1/commissions

List commissions

POST

/v1/commissions/{id}/approve

Approve a commission

GET

/v1/sales

List sales

POST

/v1/payout_batches

Generate a payout batch

GET

/v1/links

List links

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

A

AffiliateRail API

- Foundational (C-)
51/100
98
Foundational Compliance
67
Developer Experience & Jentic Compatibility
27
AI-Readiness & Agent Experience
66
Agent Usability
60
Security
70
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
98

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

67

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4
10%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

59%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

27

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
48%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

66

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: BSignals: 1
66%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

60

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

70

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring AffiliateRail by hand means learning its bearer key with the rail_live_ or rail_test_ prefix, passing program_id on every list, and sending an Idempotency-Key on writes so a retry does not record the same sale twice. Through Jentic you install once, import AffiliateRail from the API Directory, store the key once, and your agent manages partners and commissions.

Permission scoping

AffiliateRail puts the partner id in the URL path (/v1/partners/{id}), so a rule can pin your agent to one partner and the operations you choose, such as reading sales and approving commissions. You decide which operations it may call, so deleting partners or marking payouts paid stays out unless you add it.

Credential isolation

Your AffiliateRail key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'approve an affiliate commission' or 'generate a payout batch', and Jentic returns the matching AffiliateRail operation with its input schema so the agent calls the right endpoint directly.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Refersion

→

Refersion is an affiliate tracking and payout platform; AffiliateRail adds a built-in partner finder and recruitment pipeline.

Choose Refersion for established affiliate tracking; choose AffiliateRail when you also want prospect discovery and recruitment in the same API.

Alternative

Rewardful

→

Rewardful focuses on affiliate programs for subscription products; AffiliateRail exposes every program object over one REST contract.

Choose Rewardful for simple SaaS affiliate setups; choose AffiliateRail when you need fine-grained control over partners, rules, and payouts.

Alternative

Everflow

→

Everflow is a partner marketing platform for networks and advertisers; AffiliateRail covers programs, commissions, and recruitment in one API.

Choose Everflow for network-scale partner management; choose AffiliateRail for a single-contract program with built-in prospecting.

Complementary

Stripe

→

Stripe processes the actual money movement; AffiliateRail computes the commissions and payout batches that feed it.

Use AffiliateRail to attribute and approve commissions, and Stripe to move the funds when a payout batch is ready.

FAQs

Specific to using AffiliateRail API through Jentic.

What authentication does the AffiliateRail API use?

The AffiliateRail API authenticates with a key sent as a bearer token in the Authorization header, per its OpenAPI spec. A test-mode key stamps responses as test but reads and writes the same data as a live key, so the prefix labels the key rather than separating the rows. Through Jentic the key is stored encrypted on your own instance and injected at call time.

Is there an AffiliateRail MCP server?

You don't need an MCP server to give your agent AffiliateRail. Jentic connects it directly from the API Directory: import AffiliateRail, store your key once, and your agent manages partners, commissions, and payouts straight away. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

Can I limit what my agent is allowed to do with the AffiliateRail API?

Yes. Because the partner id travels in the URL path, you can write a rule that allows only reading sales and approving commissions on one partner, so the agent handles that partner and nothing else. Deleting partners or marking payouts paid stays out of the rule unless you add it, and every call the agent makes is logged.

Can I manage commissions and payouts with the AffiliateRail API?

Yes. Commission rules attribute earnings on recorded sales in integer minor units with an explicit currency, and commissions can be approved, rejected, or created manually. You can read what matures between two dates, generate a payout batch from approved commissions, and mark individual payouts paid.

What are the rate limits for the AffiliateRail API?

The AffiliateRail OpenAPI spec does not publish numeric request rate limits. It does support an Idempotency-Key header on writes so a retried request replays the first response for 24 hours instead of running the work twice. Check the AffiliateRail documentation at https://docs.affiliaterail.com for current limits.

How do I approve a commission with the AffiliateRail API through Jentic?

Search the Jentic API Directory for an intent like 'approve an affiliate commission', import AffiliateRail, and store your key once. Your agent then lists pending commissions and approves the valid ones through Jentic. To run it on your own infrastructure, install Jentic One from its GitHub repo.

GET STARTED

Start building with AffiliateRail API

Explore with Jentic One
View OpenAPI Document