MERX
MERX provides a platform for buying and selling TRON energy, enabling payments and automation on the TRON blockchain. Users can view market conditions, place energy orders, set optional price limits, and integrate the service via REST and MCP APIs. The service targets AI developers, businesses, and individual users seeking programmable energy transactions, analytics, and automated workflows.
MERX publishes 2 API contracts indexed on the APIs.io network: Payments API and TRON API. Tagged areas include Energy, Blockchain, Payments, Automation, and Artificial Intelligence.
The MERX catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.
MERX’s developer surface includes CLI, authentication, documentation, API reference, getting-started guide, pricing, engineering blog, and 21 more developer resources.
Kin Score
Standards implemented 3
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.
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
MERX Payments API
The Payments API from MERX — 5 operation(s) for payments.
MERX TRON API
The TRON API from MERX — 7 operation(s) for tron.
Event Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Merx Exchange Webhooks
ASYNCAPISpectral Rules 1
Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.
MERX API Rules
SPECTRALSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access (API Evangelist recommendations) 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll for all 7
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Source (apis.yml)
MERX API — frequently asked questions
Does MERX have an API?
Yes. APIs.io lists 2 APIs from MERX, including MERX Payments API and MERX TRON API.
Is there an OpenAPI specification for the MERX API?
Yes. APIs.io indexes 2 OpenAPI specifications for MERX, each linked for download from this page.
How do I authenticate with the MERX API?
MERX uses bearer-token authentication (2 schemes). The details are profiled on APIs.io as MERX Authentication.
Is the MERX API ready for AI agents?
MERX has a Kin Score of 44.0 out of 100 (developing) and an Agent Readiness score of 34.3 (agent-ready), scored by API Evangelist on 2026-11-21.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.