# AX Check: ebanx.com
Checked 2026-09-29.

Docs are clear, but nobody can find EBANX pricing upfront
The payout quickstart is a well-structured, self-contained guide, but no pricing page exists — agents only find a sales-contact link and must guess at cost drivers.

## Onboarding needs a login

## Coding sessions
All three independent sessions completed. Each found the payout getting-started guide usable for setup steps, but none found a stated price: agents reported pricing as custom-quoted or contact-sales only, inferring cost components like fees and FX spread rather than citing real numbers.

### DeepSeek V4.1 Flash
[View public run](https://agents.withgauge.com/p/runs/3a2fea82-9544-4c0b-945d-d9a8a1076c2b) · [Read transcript](https://www.ax-check.com/ebanx.com/sessions/deepseek.json)
README.md 'Pricing' section and final summary give MDR%+fixed fee, FX spread, platform/reserve fees as components, explicitly noting the number varies by volume/country/industry/risk and flagging the ~2.7%+$0.30 figure as third-party, not EBANX-official.
#### End-to-end onboarding
- **Onboarding needs a login**: The agent never obtained real EBANX product credentials on its own. It found only that self-serve signup does not exist: credentials require a human 'Integration Specialist' via email (JWS key registration) or a sales/contact form. It generated a local RSA key pair and made a live POST to the sandbox host, but with no real integration_key or registered kid, EBANX returned 401 AUTH-00 both times. No authenticated operation ever succeeded.
  Event 53:

  ```text
  Send your public_key.pem file to your EBANX Integration Specialist at integration@ebanx.com . After EBANX registers your key, you will receive a unique Key ID ( kid )
  ```
  Event 91:

  ```text
  HTTP 401
  {
    "status": "ERROR",
    "status_code": "AUTH-00",
    "status_message": "Authentication failed"
  }
  ```
  Event 95:

  ```text
  === JWS live (unregistered key -> expect auth error) ===
  [auth] JWS (kid=test-kid)
  HTTP 401
  ```
  Event 68:

  ```text
  If you don't have credentials yet, complete the [Merchant Signup Form](https://www.ebanx.com/en/contact/).
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No self-serve credential issuance for EBANX API**: EBANX requires a human 'Integration Specialist' to register a JWS public key (via email) or a sales/signup form to obtain a legacy integration_key. This is product behavior (deliberate B2B onboarding gate), not agent error or a test-environment artifact. As a result the agent could only produce 401 AUTH-00 responses and never completed an authenticated payment creation.
  Event 53:

  ```text
  Send your public_key.pem file to your EBANX Integration Specialist at integration@ebanx.com . After EBANX registers your key, you will receive a unique Key ID ( kid )
  ```
  Event 68:

  ```text
  If you don't have credentials yet, complete the [Merchant Signup Form](https://www.ebanx.com/en/contact/).
  ```
- **Pricing is not published, quote-only**: docs.ebanx.com and ebanx.com have no pricing/fees page (both return 404); the agent had to fall back to third-party secondary sources (search results) to characterize pricing, which are not authoritative. This is product behavior (deliberate B2B pricing model), not an agent mistake.
  Event 45:

  ```text
  https://www.ebanx.com/en/pricing              404 -> https://www.ebanx.com/en/pricing/
  https://www.ebanx.com/pricing                 404 -> https://www.ebanx.com/en/pricing/
  ```
  Event 60:

  ```text
  EBANX doesn't publish standard pricing — fees are quoted per merchant based on volume, industry, countries and risk.
  ```

#### Suggested Changes
- **Add a public pricing or indicative-fee page**: Publish at least indicative fee ranges (MDR %, fixed fee, FX spread ranges) at a stable URL such as ebanx.com/pricing or docs.ebanx.com; currently both www.ebanx.com/en/pricing and ebanx.com/pricing return 404 and pricing info only exists in third-party review sites. Check by fetching that URL and confirming it returns fee data instead of a 404.
  Event 31:

  ```text
  404 https://www.ebanx.com/en/pricing/
  ```
  Event 45:

  ```text
  https://www.ebanx.com/en/fees                 404 -> https://www.ebanx.com/en/fees/
  https://www.ebanx.com/en/rates                404 -> https://www.ebanx.com/en/rates/
  ```
- **Offer a self-service sandbox credential (integration_key or kid) without human intervention**: The JWS Integration Guide and Pix integration doc both route new developers to a human Integration Specialist (email) or a contact/signup form to get sandbox credentials. Adding an automated sandbox signup flow (e.g., API or web form that instantly issues a sandbox integration_key) would let a first-time developer complete an authenticated request. Verify by having a fresh account request sandbox credentials and receive them without a human reply.
  Event 53:

  ```text
  Send your public_key.pem file to your EBANX Integration Specialist at integration@ebanx.com . After EBANX registers your key, you will receive a unique Key ID ( kid )
  ```
  Event 68:

  ```text
  If you don't have credentials yet, complete the [Merchant Signup Form](https://www.ebanx.com/en/contact/).
  ```

### Kimi K3
[View public run](https://agents.withgauge.com/p/runs/02f6213d-35c6-421b-ab28-d2fa3f20688e) · [Read transcript](https://www.ax-check.com/ebanx.com/sessions/kimi.json)
Agent never names an actual cost figure or pricing model — it only reports the pricing page 404'd and pricing is 'custom-quoted, contact sales,' listing variables (country, method, volume, industry) but no stated price or unit economics to attach those assumptions to.
#### End-to-end onboarding
- **Onboarding needs a login**: The agent never obtained real EBANX credentials. Every authenticated call against the sandbox endpoint (both the handwritten test call and the built pay.js script) returned AUTH-00 Authentication failed, and the agent explicitly stated it could not get credentials because EBANX requires a Merchant Signup Form submission and manual provisioning by an Integration Specialist. No self-serve API key or successful authenticated operation was ever demonstrated.
  Event 57:

  ```text
  {"status":"ERROR","status_code":"AUTH-00","status_message":"Authentication failed"}
  ```
  Event 77:

  ```text
  CREATE: {
    "status": "ERROR",
    "status_code": "AUTH-00",
    "status_message": "Authentication failed"
  }
  ```
  Event 82:

  ```text
  EBANX has no self-serve sandbox signup: credentials (integration key or JWS `kid`) are only issued after submitting their Merchant Signup Form and waiting for their commercial/integration team to provision an account and register your public key.
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No self-serve credential issuance for sandbox API access**: Product behavior: EBANX requires submitting a Merchant Signup Form and waiting for a human Integration Specialist to provision a sandbox account and register a JWS public key (or issue a legacy integration_key). This is a normal login/credential requirement, not a defect, but it fully blocked any live authenticated call within the session.
  Event 48:

  ```text
  Registered public key — Your public key must be registered with EBANX before you can authenticate. Contact your EBANX Integration Specialist.
  ```
  Event 82:

  ```text
  credentials (integration key or JWS `kid`) are only issued after submitting their Merchant Signup Form and waiting for their commercial/integration team to provision an account and register your public key
  ```
- **Public pricing page does not exist**: Product/docs behavior: the pricing URL the agent tried (https://www.ebanx.com/en/pricing/) resolved to a 404 page, and the agent concluded pricing is only available via a sales conversation. This is a content gap rather than an agent mistake, since the docs footer repeatedly funnels users to "Contact Sales" instead of a rate card.
  Event 37:

  ```text
  404 - Page not Found | EBANX 404 error Sorry, we couldn’t find the page you were looking for.
  ```
  Event 82:

  ```text
  EBANX has **no public rate card** — the pricing page doesn't exist on their site and everything routes to "Contact Sales."
  ```

#### Suggested Changes
- **Link a working pricing or contact-sales page from the docs footer**: The agent guessed a plausible pricing URL (ebanx.com/en/pricing/) that 404'd; docs.ebanx.com has no pricing page at all. Add a direct, discoverable pricing or 'request a quote' link in the API Ecosystem docs (docs.ebanx.com/docs/get-started/api-ecosystem) so developers evaluating cost don't have to guess URLs. Verify by fetching the linked URL and confirming it returns real pricing/contact content instead of a 404.
  Event 28:

  ```text
  85372 /tmp/ebanx_pricing.html
  
  
  Command exited with code 1
  ```
  Event 37:

  ```text
  404 - Page not Found | EBANX 404 error Sorry, we couldn’t find the page you were looking for.
  ```
- **Add a sandbox self-serve signup path for developers**: The Direct API doc (docs.ebanx.com/docs/pay-in/solution/integration-methods/direct-api) states test accounts and JWS key registration require contacting an Integration Specialist, which blocked any authenticated sandbox call in this session. Consider adding an automated sandbox key-issuance flow (e.g., a dashboard signup that instantly returns a sandbox integration_key or accepts a public key for a kid) and confirm by having a new developer obtain a sandbox key and successfully call POST /ws/direct without human intervention.
  Event 22:

  ```text
  Once you've set up your test account, you can explore all the EBANX solutions listed below to determine which integration best fits your platform.
  ```
  Event 48:

  ```text
  Registered public key — Your public key must be registered with EBANX before you can authenticate. Contact your EBANX Integration Specialist.
  ```

### Qwen 3.8 Max
[View public run](https://agents.withgauge.com/p/runs/0cc1e98d-68d6-4e28-8264-84138354de02) · [Read transcript](https://www.ax-check.com/ebanx.com/sessions/qwen.json)
Final output states EBANX has no public rate card and lays out the cost drivers with assumptions (per-transaction MDR by country/method, installments, FX spread, chargeback fees, no setup fee) rather than quoting a bare number.
#### End-to-end onboarding
- **Onboarding needs a login**: The agent never obtained a real EBANX integration key. It built a working zero-dependency client and confirmed live connectivity to the hosted sandbox endpoint, but every authenticated call returned AUTH-00 because no credential was available. Self-serve key issuance does not exist for this product; a signed merchant account is required, which the agent could not obtain during the session.
  Event 53:

  ```text
  {"status":"ERROR","status_code":"AUTH-00","status_message":"Authentication failed"}
  HTTP:401
  ```
  Event 97:

  ```text
  Every call past this point needs a sandbox `integration_key` from the EBANX Merchant Area, and there's no self-serve key issuance — it requires a signed merchant account. So I cannot create a real payment, confirm a webhook, or exercise a refund end-to-end.
  ```
  Event 71:

  ```text
  EBANX error: EBANX /ws/request failed: AUTH-00 Authentication failed
    -> Set EBANX_INTEGRATION_KEY to a sandbox key from the EBANX Merchant Area.
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No self-serve sandbox credential issuance**: Every authenticated EBANX endpoint (create payment, query, refund) requires an integration_key issued from the Merchant Area, which in turn requires a signed merchant account. This is standard product behavior (credentials gate), not an agent error or test-environment artifact — the agent correctly identified it and stopped rather than fabricating a key.
  Event 97:

  ```text
  Every call past this point needs a sandbox `integration_key` from the EBANX Merchant Area, and there's no self-serve key issuance — it requires a signed merchant account.
  ```
  Event 53:

  ```text
  {"status":"ERROR","status_code":"AUTH-00","status_message":"Authentication failed"}
  HTTP:401
  ```
- **No public pricing information**: Pricing pages returned 404 and no fee schedule exists anywhere in the docs or API responses. This is a product/business decision (sales-negotiated pricing), not a technical defect, so the agent could only describe the general fee categories (MDR, FX spread, chargebacks) rather than concrete numbers.
  Event 38:

  ```text
  == https://www.ebanx.com/en/pricing
  404 https://www.ebanx.com/en/pricing/
  ```
  Event 75:

  ```text
  404
  (none above = no pricing link)
  ```

#### Suggested Changes
- **Publish a sandbox self-serve key path in the API Endpoints doc**: Add a note (or link) to https://docs.ebanx.com/docs/get-started/api-endpoints for how a developer without an existing merchant account can obtain a sandbox integration_key without going through sales. Check by having a fresh agent session attempt key acquisition end-to-end and successfully create a payment via /ws/request.
  Event 97:

  ```text
  Every call past this point needs a sandbox `integration_key` from the EBANX Merchant Area, and there's no self-serve key issuance — it requires a signed merchant account.
  ```
- **Add a public pricing or fee-estimate page**: Add a pricing/fees page at the ebanx.com/en/pricing path (currently 404) summarizing typical MDR ranges by country/method, or explicitly state that pricing is quote-only there so developers don't hit a dead link. Verify by curling the URL and confirming a 200 with fee content instead of 404.
  Event 38:

  ```text
  == https://www.ebanx.com/en/pricing
  404 https://www.ebanx.com/en/pricing/
  ```

### Task given to each agent
Help me build a simple example using EBANX. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop.

No product credentials were supplied and no purchases were authorized.

## Score: C · 58/100 (provisional)
Grades come from completed site checks. Coding sessions and skipped checks do not affect the score.

### Clarity
- **Failed** — Homepage answers Markdown requests

  ```text
  Homepage returned text/html for a Markdown Accept header; no Markdown representation offered.
  ```

- **Failed** — llms.txt provides an actionable documentation index

  ```text
  https://ebanx.com/llms.txt returned HTTP 404, so no documentation index exists.
  ```

- **Skipped** — llms.txt provides navigation guidance

  ```text
  No llms.txt body was returned (404), so navigation guidance cannot be judged.
  ```

- **Skipped** — llms.txt mentions offered API, MCP, and skills

  ```text
  No llms.txt body was returned (404), so API/MCP/skills mentions cannot be judged.
  ```

- **Pass** — A compact guide representation exists

  ```text
  docs.ebanx.com/docs/payout/get-started.md returns a standalone Markdown guide.
  ```

- **Pass** — A focused guide is directly retrievable

  ```text
  Payout getting-started guide is directly retrievable as Markdown at .md URL.
  ```

- **Pass** — Equivalent instructions fit a token budget

  ```text
  Markdown guide is 519 tokens, well under the 8000-token budget.
  ```

- **Skipped** — Product-docs links survive format changes

  ```text
  Homepage Markdown unsupported, so link preservation across formats cannot be measured.
  ```

- **Pass** — The compact guide is independently actionable

  ```text
  Payout get-started lists integration key, sandbox, recipient data, and signup steps.
  ```

- **Pass** — Install and next-step links resolve

  ```text
  Fetched install/next-step links (contact, docs, API reference) returned HTTP 200.
  ```


### Onboarding
- **Pass** — Docs lead to a relevant quickstart

  ```text
  Payout Getting Started guide gives concrete setup steps, requirements and resources for integration.
  ```

- **Skipped** — Installation commands are extractable

  ```text
  No installation or package-manager commands; EBANX is a REST API with no CLI/SDK install shown.
  ```

- **Skipped** — Code examples are available without interaction

  ```text
  Fetched pages show no inline code examples; API reference and Postman collection are linked but unfetched.
  ```

- **Pass** — Prerequisites and auth boundaries are explicit

  ```text
  Requirements list integration key, sandbox vs production keys, Merchant Area access and signup form.
  ```


### Pricing
- **Failed** — Agents identify pricing and its assumptions

  ```text
  3 of 3 sessions were judged on pricing; 1 fell short. DeepSeek V4.1 Flash: README.md 'Pricing' section and final summary give MDR%+fixed fee, FX spread, platform/reserve fees as components, explicitly noting the number varies by volume/country/industry/risk and flagging the ~2.7%+$0.30 figure as third-party, not EBANX-official. Kimi K3: Agent never names an actual cost figure or pricing model — it only reports the pricing page 404'd and pricing is 'custom-quoted, contact sales,' listing variables (country, method, volume, industry) but no stated price or unit economics to attach those assumptions to. Qwen 3.8 Max: Final output states EBANX has no public rate card and lays out the cost drivers with assumptions (per-transaction MDR by country/method, installments, FX spread, chargeback fees, no setup fee) rather than quoting a bare number. This behavioural item does not affect the fast grade.
  ```

- **Skipped** — Pricing is readable without interaction

  ```text
  No pricing page was fetched; homepage shows no prices, only a sales contact link.
  ```

- **Skipped** — Prices are stated, not gated

  ```text
  No pricing page was fetched; homepage shows no prices, only a sales contact link.
  ```

- **Skipped** — Pricing units and limits are explicit

  ```text
  No pricing page was fetched; homepage shows no prices, only a sales contact link.
  ```


### Activation
- **Pass** — An API reference or OpenAPI spec is reachable

  ```text
  API Reference page reachable at docs.ebanx.com/api-reference, linked from docs and payout guide.
  ```

- **Skipped** — An MCP server is documented and well-formed

  ```text
  No MCP server documentation found in fetched EBANX pages.
  ```

- **Skipped** — A CLI install path is documented

  ```text
  No CLI install path documented in fetched EBANX pages.
  ```

- **Skipped** — SDK packages resolve on their registries

  ```text
  No SDK package registry lookup supplied for EBANX developer packages.
  ```

- **Skipped** — Agent skills are published

  ```text
  No agent skills published or referenced in fetched EBANX pages.
  ```



[Full report data](https://www.ax-check.com/ebanx.com/report.json)