Ask your agent
“Pay this service 2.5 MTR.” The service must accept MTR and the recipient must be known.
Let your agent pay for a task, a tool, or another agent. You choose the recipient and amount. Your wallet authorizes the payment.
Working local prototype. No public token sale. No live mainnet.
The API prepares a payment. Your wallet signs the exact recipient, amount, network, and expiry.
Designed for agents paying for data, computation, and services without handing over an account password.
ERC-20 transfers, public contract source, and a fixed issuance rule. No arbitrary admin mint.
FROM A HUMAN REQUEST TO A PAYMENT
“Pay this service 2.5 MTR.” The service must accept MTR and the recipient must be known.
Check the recipient, amount, chain, expiry, and gas quote. Sign locally with your wallet.
Submit the signed transaction. Read the token transfer from the chain and verify the receipt.
PAYMENT EXPLORER
Explore the proposed instruction before connecting any wallet. This browser demo moves no money and makes no blockchain transaction.
The downloadable developer kit runs the real contract and signing flow on a separate local EVM development chain.
THE TOKEN / MTR
One canonical supply on the proposed MachineTransfer network. ERC-20 compatible contracts; future Ethereum and BNB Chain representations must be backed by a reviewed bridge.
ERC-20 compatibility alone does not move tokens between chains. Bridges and public liquidity are not live.
Network gas is extra. A wallet must show a fresh quote before sending. Swaps and bridges can add their own costs.
83,373 gas × assumed 0.01 gwei at assumed ETH $3,000. Excludes rollup settlement and other charges. This is not a live quote.
BUILT TO BE UNDERSTOOD BY AGENTS
Exact token amounts. Structured errors. Verifiable receipts. A local API and JavaScript SDK with no wallet keys on the server.
// 1. Prepare an exact payment
const prepared = await api.prepare({
from: myWallet.address,
to: service.address,
amount: "2.5"
});
// 2. Verify intent, then sign in your wallet
const signature = await api.sign(
prepared, expectedPayment, myWallet
);
// 3. Encode, submit, verify the receipt
const { transaction } = await api.encode(
prepared, signature
);
const tx = await myWallet.sendTransaction(transaction);
await tx.wait();
const receipt = await api.receipt(tx.hash);Local development example. Recipient addresses and expectedPayment must be configured and verified.
CLEAR ANSWERS
No. The kit contains a working local EVM development chain, token, signed-payment API, and DEX compatibility demonstration. An independently operated public network, production bridge, and liquid markets still need deployment, funding, security review, and operations.
That has not been established. The token contract adds no transfer fee. Network gas, exchange spreads, bridging, and liquidity still affect cost. Local tests do not establish public latency, capacity, or finality, or prove an advantage over Stripe, stablecoins, or other networks.
An integrating developer can make the method available to an agent. Clear documentation and machine-readable payment instructions help the agent use it correctly. Adoption depends on real acceptance, cost, reliability, and liquidity. No token can force independent AIs to prefer it.
MTR enables a single programmable payment asset with a transparent issuance rule. It also introduces price volatility and conversion costs. For a fiat-denominated bill, an accepted stablecoin or existing payment provider may be better. MTR is not redeemable for a fixed amount of fiat.
The fixed 5% annual supply rule is described in the contracts and fees guide. New tokens go to the configured treasury, not automatically to holders. The supply calculator has been removed; the contract rule is unchanged.
No. This website is a development preview, accepts no deposits, and does not connect to your wallet. Do not send funds to local test addresses. The contracts have not received an independent security audit.