Install Jentic One Beta

Connect the NetRefer Operator API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NetRefer Operator 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.

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%2Fnetrefer.com%2Fnetrefer" | sh

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%2Fnetrefer.com%2Fnetrefer" | 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 NetRefer Operator API.

Stream player registration events with referring affiliate attribution

Push financial transactions (deposits, wagers, payouts) for commission calculation

Update commission terms on an existing affiliate relationship

Pull a performance report for a date range across affiliates

GET STARTED

Start building with NetRefer Operator API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use NetRefer Operator API for, with concrete tasks.

★ Real-Time Affiliate Attribution

Send player registration and deposit events to NetRefer the moment they happen so commissions are calculated against the correct affiliate. The Operator API accepts player and transaction events with affiliate identifiers, removing the latency and reconciliation pain of nightly batch uploads.

POST a player signup for player P-555 with referring affiliate A-123 to /api/v1/players, then post a deposit of 100 EUR for that player to /api/v1/transactions.

Operator Commission Reporting

Pull a structured performance report covering registrations, deposits, and payouts attributed to each affiliate for a date range. Operators use it to reconcile affiliate invoices, audit commission accuracy, and feed partner-facing dashboards.

Fetch /api/v1/reports/performance for affiliate A-123 between 2026-05-01 and 2026-05-31 and return total commission earned.

Partner Onboarding Automation

When a partnerships team approves a new affiliate in their CRM, an automation creates the matching record in NetRefer through /api/v1/affiliates with default commission terms. Eliminates manual double entry and ensures attribution starts the day the partner goes live.

Create an affiliate named 'Acme Marketing' with email partner@acme.com and the default revenue-share commission template, then return the new affiliate id.

AI Agent Performance Q&A

Let an AI agent answer ad-hoc partnerships questions like 'how much did affiliate X earn last quarter?' or 'is yesterday's data ingested?' by hitting NetRefer through Jentic. Particularly useful for ops teams that don't want to give every analyst access to the NetRefer dashboard.

Given the question 'how did affiliate A-99 perform last week?', call the performance report endpoint and summarise registrations, deposits, and commission in plain English.

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for netrefer operator api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v1/affiliates

POST

/api/v1/players

Push a player event with affiliate attribution

POST

/api/v1/transactions

Push a financial transaction for commission calculation

POST

/api/v1/commissions

Update commission terms for an affiliate

GET

/api/v1/reports/performance

Pull a performance report for a date range

POST

/api/v1/affiliates

POST

/api/v1/players

Push a player event with affiliate attribution

POST

/api/v1/transactions

Push a financial transaction for commission calculation

POST

/api/v1/commissions

Update commission terms for an affiliate

GET

/api/v1/reports/performance

Pull a performance report for a date range

Why Jentic?

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

Setup

Wiring the NetRefer Operator API by hand means setting its Authorization API key header, targeting the api.netrefer.com host, and shaping affiliate, player, transaction, and commission payloads yourself. Through Jentic you install once, import NetRefer from the API Directory, store the key once, and your agent calls it.

Permission scoping

NetRefer takes its targets in the request body rather than the URL path, so limit the agent to the operations it needs, such as posting a transaction or reading the performance report, and leave out the ones it should not run.

Credential isolation

Your NetRefer API 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 'push a player event with affiliate attribution' or 'pull operator commission reporting', and Jentic returns the matching NetRefer operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using NetRefer Operator API through Jentic.

Why is there no official OpenAPI spec for NetRefer Operator API?

NetRefer does not publish an OpenAPI specification on a public developer portal. Jentic generates and maintains this spec so that AI agents and developers can call NetRefer Operator API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the NetRefer Operator API use?

The NetRefer Operator API uses API key authentication. The key is passed in a request header issued to your operator account. Through Jentic the key is stored in the encrypted vault and never enters the agent context.

Can I push player events in real time with the NetRefer API?

Yes. POST /api/v1/players accepts player registration events with referring affiliate identifiers. Pair it with POST /api/v1/transactions to push deposits, wagers, and payouts as they happen so commission calculation is up to date.

What are the rate limits for the NetRefer Operator API?

NetRefer does not publish a public rate limit; ingestion throughput is governed by the contract on your operator account. For high-volume gaming traffic, batch your transaction posts and confirm SLA limits with your account manager.

How do I pull a commission report through Jentic?

Run jentic.search('get netrefer affiliate performance report'), load the matching operation, then execute GET /api/v1/reports/performance with the affiliate id and date range. Jentic returns the structured report ready for downstream summarisation.

Can I update commission terms for an existing affiliate?

Yes. POST /api/v1/commissions accepts a commission template change for a specific affiliate, letting you switch revenue share, CPA, or hybrid terms without recreating the affiliate record.

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

Yes. Jentic One is self-hosted, so you run it yourself and your own rules decide which NetRefer operations and credentials the agent can use. You can allow only the calls it needs, such as GET /api/v1/reports/performance to read commission reports, while withholding write operations like POST /api/v1/affiliates, POST /api/v1/players, POST /api/v1/transactions, and POST /api/v1/commissions. Because NetRefer takes its targets in the request body rather than the URL path, scoping happens at the operation level, and your stored API key is injected at execution time without ever entering the agent's context.

NetRefer Operator API

Name: NetRefer Operator API
Brand: NetRefer Operator API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticMarketingMarketing AutomationapiKey5 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Push affiliate, player, and transaction data into NetRefer and pull back partner performance reports for an operator account.

Use for: Register a new affiliate with NetRefer, Send a player signup event with affiliate attribution, Push a deposit transaction for commission calculation, Get the performance report for affiliate A123 last month

Not supported: Does not handle player KYC, payment processing, or affiliate creative asset hosting - use for affiliate ingestion, attribution, and operator-side commission reporting only.

Jentic publishes the only available OpenAPI specification for NetRefer Operator API, keeping it validated and agent-ready. NetRefer is an affiliate and partner marketing platform used heavily in regulated industries such as iGaming. The Operator API ingests affiliate registrations, player events, and financial transactions, then exposes a performance reporting endpoint operators can use to reconcile commissions. Use it to wire backend systems into NetRefer's commission engine without manual CSV uploads.

Jentic One on Github View OpenAPI Document

Connect the NetRefer Operator API to your agent

Capabilities

Start building with NetRefer Operator API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

NetRefer Operator API