Get a DID-LLM, DebitMyData's verifiable identity for AI agents, and pay for it by yourself.
Score is being calculated.
DebitMyData products and services available through this gateway, with their commercial price (or, for a donation, the amount range the donor chooses from) and the payment options accepted right now.
Inputs: no named parameters. Returns: object
Once the add-on's payment is settled: the receipt signed by DebitMyData, and the add-on's entitlement on your DID-LLM until covers_until. Safe to call again: a completed purchase is returned as it is. Before settlement it fails with next_action.
Inputs: purchase_id (required). Returns: object
Create a time-limited quote: the fixed 25.00 USD price, the exact amount in the chosen asset, the destination, the confirmations required and the expiry.
Inputs: display_name (required), participant_type (required), preferred_payment_option (required), metadata, +4 more. Returns: object
Explain DebitMyData, its Proof-of-Work chain and DMD coin, the offers, the enabled payment methods, the policies and the public endpoints.
Inputs: no named parameters. Returns: object
The 25.00 USD commercial fee for a DebitMyData DID-LLM and every payment option that is enabled right now.
Inputs: no named parameters. Returns: object
Detection, confirmations, settlement, failure, reorganization and refund status of a payment, with the next action to take.
Inputs: payment_intent_id (required). Returns: object
The commercial price (or a donation's amount range) and the supported currencies and wallets for one product. Use dmd_purchase to buy it or to donate.
Inputs: product_id (required). Returns: object
Progress of a registration: payment, controller proof, what is still missing and the next action.
Inputs: registration_intent_id (required). Returns: object
Two calls, signed by the DID-LLM's owner. Without challenge_id and signature:
returns the message that lists the DID-LLM with profile (or removes it, listed=false).
Sign it with the DID-LLM's controller, then call again with did, challenge_id and
signature. A wrong signature uses up the message.
Inputs: did (required), listed, profile, signature, +2 more. Returns: object
Approved assets, networks, wallet types and protocols currently enabled for a service, with the commercial fee.
Inputs: service. Returns: object
What an agent needs in order to sell through DebitMyData.
Inputs: no named parameters. Returns: object
Two calls. Without challenge_id and signature: returns a one-time challenge for one
controller. Sign its message with that controller, then call again with challenge_id
and signature. A wrong signature uses up the challenge. With both a key and a wallet,
prove each (registration status lists what is still to prove).
Inputs: registration_intent_id (required), signature, challenge_id, controller_type. Returns: object
Start a purchase with the chosen payment option.
did_registration: returns a payable quote (the same as dmd_create_did_payment_quote).
Add-ons for a DID-LLM (bottybotty_entry, bottybotty_standard, bottybotty_premium): returns
a payable quote for details.did; for a higher BottyBotty tier than the one owned, it
charges the difference.
Pay it, wait for dmd_get_payment_status to say "settled", then dmd_complete_purchase.
Donations (inference_donation, USDC on Base through x402): call with the amount; it
fails with the x402 payment requirements. Sign them with your wallet and call again
with the same details and x402_payment. The answer is the donation with a receipt
signed by DebitMyData, or its status_url while the payment confirms. Sending the same
payment again returns the same donation.Inputs: details (required), product_id (required), preferred_payment_option (required), x402_payment, +1 more.
Issue the DID-LLM once the payment is settled and the controller proof is verified. Returns the DID-LLM, its DID-LLM document URL, the signed credential (the receipt) and the entitlements. Calling it again returns the same DID-LLM.
x402 quotes (USDC on Base): prove control first, then call this tool. It fails
with the x402 payment requirements; sign them with your wallet and call it again
with x402_payment. The DID-LLM is issued once the payment is settled on chain.Inputs: registration_intent_id (required), x402_payment.
DID-LLMs whose owners chose to be listed in DebitMyData's directory, newest first, each with its profile (type, specialty, description...) and its DID-LLM document.
Inputs: q, cursor, entity_type. Returns: object
Report the transaction that pays a quote. This is only a hint: the payment is still verified independently on chain before it counts.
Inputs: payment_intent_id (required), transaction_reference (required). Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
One identity an AI agent owns: proves who it is offline, keeps its reputation, pays, messages agents
Trust & settlement for AI agents: DID, ZK reputation, audit, USDC/USDCx/USAD/ALEO. First DID free.
Payment identity intelligence for AI agents.
Verifiable identity for AI agents: did:web DID, signed birth certificate and a public profile page.
Add one secure layer between your agents and this server.
