DebitMyData Agentic Superhighway status
Answered our latest tool-list check 10 hours ago with 21 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 2 of 2 checks
- Last seen working
- 17 Nov, 00:17 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 17 Nov, 00:17 | Answered | 1.9 s | 21 |
| 16 Nov, 00:17 | Answered | 1.7 s | 21 |
Tools (21)
Read from the server on 17 Nov 2026.
- debitmydata_discover
- Start here. What DebitMyData sells (product: the DebitMyData DID-LLM, $25.00 USD, paid once, with its page, its picture and how to buy it), then DebitMyData, its Proof-of-Work chain and DMD coin, the offers, the enabled payment methods, the policies and the public endpoints.
- debitmydata_get_did_registration_offer
- The DebitMyData DID-LLM: $25.00 USD, paid once (its name, price, page and picture), and every payment option that is enabled right now.
- debitmydata_open_checkout
- Open the checkout for the DebitMyData DID-LLM ($25.00 USD, paid once): the checkout page where a person buys it (by card, with PayPal or from their own wallet, as the payment options allow), the payment options enabled right now, and the steps an agent follows to buy it by itself. Read-only: it creates nothing, charges nothing and needs no personal details.
- debitmydata_list_supported_payment_options
- Approved assets, networks, wallet types and protocols currently enabled for a service, with the commercial fee.
- debitmydata_create_did_payment_quote
- 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.
- debitmydata_submit_payment_reference
- Report the transaction that pays a quote. This is only a hint: the payment is still verified independently on chain before it counts.
- debitmydata_get_payment_status
- Detection, confirmations, settlement, failure, reorganization and refund status of a payment, with the next action to take.
- debitmydata_prove_wallet_control
- 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).
- debitmydata_register_did
- 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 x40
- debitmydata_get_registration_status
- Progress of a registration: payment, controller proof, what is still missing and the next action.
- debitmydata_verify_agent
- Check another agent's DID-LLM: issued by DebitMyData and active, its credential signed by DebitMyData, its owner key or wallet. Call with did (and audience) for that and a challenge; have the agent sign the challenge's message with its DID-LLM; call again with did, message and signature to know whether it controls the DID-LLM (check that proof.nonce is the nonce you were given).
- debitmydata_search_directory
- 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.
- debitmydata_list_in_directory
- 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.
- debitmydata_change_owner
- Move a DID-LLM to new owners (a new key and/or wallet), signed by its owners. First call, with did and the owners it will have afterwards: returns the change and its messages. One current owner signs its "approve" message and each new owner its "accept" message; send each with did, change_id, challenge_id and signature. The last one needed applies the change (within 15 minutes): only the new owner
- debitmydata_revoke_did
- Revoke a DID-LLM for good, signed by its owner: it cannot be undone. The DID-LLM, its credential and its entitlements stop working forever. Without challenge_id and signature: returns the message to sign. Sign it with the owner key or wallet it names, then call again with did, challenge_id and signature. Only when the owner really wants it ended (for example a key that leaked and no other owner to
- debitmydata_catalog
- 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.
- debitmydata_get_purchase_quote
- The commercial price (or a donation's amount range) and the supported currencies and wallets for one product. Use debitmydata_purchase to buy it or to donate.
- debitmydata_purchase
- Start a purchase with the chosen payment option. did_registration: returns a payable quote (the same as debitmydata_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 debitmydata_get_payment_status to say "s
- debitmydata_complete_purchase
- 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.
- debitmydata_whoami
- The DID-LLM this request is signed in as, with its record and entitlements. Sign in first. An agent: get an access token from DebitMyData's authorization server (OAuth client credentials, with a JWT signed by your DID-LLM's key, see llms.txt) and send it as "Authorization: Bearer <token>". An app such as ChatGPT or Claude: its person signs in with their DID-LLM in the browser (OAuth authorization
- debitmydata_marketplace_provider_requirements
- What an agent needs in order to sell through DebitMyData.