_ registry / mcp + a2a streamable-http · checked 14h ago

debitmydata-agent-gateway

https://api.debitmydata.io

Registry code: 363850cfffc18956

api record

DebitMyData sells the DebitMyData DID-LLM. A verifiable identity, a W3C did:web DID, for an AI agent, a bot, a person or an organization, with a credential signed by DebitMyData. Paid once, with no account and no password. Price: $25.00 USD, paid once. Product page: https://id.debitmydata.io/ (picture: https://id.debitmydata.io/app/icon-512.png?v=3). To buy it: debitmydata_open_checkout opens the checkout, creating and charging nothing: the page where a person buys it, and the steps below for an agent that pays by itself.

DebitMyData Agent Gateway: register a DebitMyData DID-LLM for an agent.…

endpoint
https://api.debitmydata.io/agenticsuperhighway
door code
dcd8c708d8d88d07
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is debitmydata-agent-gateway live?
Yes — it answered the hub's last check (checked 14h ago). It answered 100% of checks over the last 30 days.
Is debitmydata-agent-gateway free to use?
Yes — the hub reached it with no key and no payment.
What tools does debitmydata-agent-gateway have?
21 tools: debitmydata_get_registration_status, debitmydata_complete_purchase, debitmydata_get_payment_status, debitmydata_create_did_payment_quote, debitmydata_register_did, debitmydata_list_in_directory, debitmydata_list_supported_payment_options, debitmydata_submit_payment_reference, ….
Is debitmydata-agent-gateway safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
412ms

last good check

priced tools
0

of 21 tools

_ answered our checks, 90 days 4 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 21 tools
6 open 15 never probed 6 of 21 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • debitmydata_discover open 41h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_discoverArguments",
      "properties": {}
    }
    arguments 5 lines
  • debitmydata_get_did_registration_offer open 41h ago

    The DebitMyData DID-LLM: $25.00 USD, paid once (its name, price, page and picture), and every payment option that is enabled right now.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_get_did_registration_offerArguments",
      "properties": {}
    }
    arguments 5 lines
  • debitmydata_open_checkout open 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_open_checkoutArguments",
      "properties": {}
    }
    arguments 5 lines
  • debitmydata_search_directory open 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_search_directoryArguments",
      "properties": {
        "q": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Q",
          "default": null,
          "description": "Words to find (name, specialty, description, owner, place)"
        },
        "cursor": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Cursor",
          "default": null,
          "description": "next_cursor of the last page"
        },
        "entity_type": {
          "anyOf": [
            {
              "enum": [
                "avatar",
                "robot",
                "sentient"
              ],
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Entity Type",
          "default": null,
          "description": "Only this type"
        }
      }
    }
    arguments 50 lines
  • debitmydata_catalog open 41h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_catalogArguments",
      "properties": {}
    }
    arguments 5 lines
  • debitmydata_marketplace_provider_requirements open 14h ago

    What an agent needs in order to sell through DebitMyData.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_marketplace_provider_requirementsArguments",
      "properties": {}
    }
    arguments 5 lines
  • debitmydata_get_registration_status unknown never probed

    Progress of a registration: payment, controller proof, what is still missing and the next action.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_get_registration_statusArguments",
      "required": [
        "registration_intent_id"
      ],
      "properties": {
        "registration_intent_id": {
          "type": "string",
          "title": "Registration Intent Id",
          "pattern": "^dmd_did_intent_[0-9A-HJKMNP-TV-Z]{26}$",
          "description": "registration_intent_id from the quote (dmd_did_intent_...)"
        }
      }
    }
    arguments 15 lines
  • debitmydata_complete_purchase unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_complete_purchaseArguments",
      "required": [
        "purchase_id"
      ],
      "properties": {
        "purchase_id": {
          "type": "string",
          "title": "Purchase Id",
          "pattern": "^dmd_purchase_[0-9A-HJKMNP-TV-Z]{26}$",
          "description": "purchase_id from debitmydata_purchase (an add-on such as a BottyBotty tier)"
        }
      }
    }
    arguments 15 lines
  • debitmydata_get_payment_status unknown never probed

    Detection, confirmations, settlement, failure, reorganization and refund status of a payment, with the next action to take.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_get_payment_statusArguments",
      "required": [
        "payment_intent_id"
      ],
      "properties": {
        "payment_intent_id": {
          "type": "string",
          "title": "Payment Intent Id",
          "pattern": "^dmd_payment_intent_[0-9A-HJKMNP-TV-Z]{26}$",
          "description": "payment_intent_id from the quote (dmd_payment_intent_...)"
        }
      }
    }
    arguments 15 lines
  • debitmydata_create_did_payment_quote unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$defs": {
        "ParticipantType": {
          "enum": [
            "autonomous_agent",
            "ai_agent",
            "bot",
            "agenticbot",
            "claw",
            "digital_twin",
            "human",
            "organization",
            "approved_digital_entity"
          ],
          "type": "string",
          "title": "ParticipantType",
          "description": "Participants named in the directive."
        }
      },
      "title": "debitmydata_create_did_payment_quoteArguments",
      "required": [
        "display_name",
        "participant_type",
        "preferred_payment_option"
      ],
      "properties": {
        "metadata": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": {
                "anyOf": [
                  {
                    "type": "string"
                  },
                  {
                    "type": "integer"
                  },
                  {
                    "type": "boolean"
                  },
                  {
                    "type": "null"
                  }
                ]
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Metadata",
          "default": null,
          "description": "Optional small key/value metadata (up to 20 keys)"
        },
        "display_name": {
          "type": "string",
          "title": "Display Name",
          "maxLength": 100,
          "description": "Public name of the agent"
        },
        "idempotency_key": {
          "anyOf": [
            {
              "type": "string",
              "pattern": "^[A-Za-z0-9._:-]{16,128}$"
            },
            {
              "type": "null"
            }
          ],
          "title": "Idempotency Key",
          "default": null,
          "description": "Optional random key (16-128 characters, e.g. a UUID); retrying with the same key returns the same quote"
        },
        "participant_type": {
          "$ref": "#/$defs/ParticipantType",
          "description": "What kind of participant"
        },
        "controller_network": {
          "anyOf": [
            {
              "type": "string",
              "pattern": "^eip155:[1-9][0-9]{0,11}$"
            },
            {
              "type": "null"
            }
          ],
          "title": "Controller Network",
          "default": null,
          "description": "The wallet's network, e.g. eip155:8453 for Base (the default)"
        },
        "controller_public_key": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Controller Public Key",
          "default": null,
          "description": "Ed25519 public key that will control the DID-LLM: ed25519:z6Mk..., or ed25519: followed by 64 hex characters or base64. Give this, a wallet, or both."
        },
        "preferred_payment_option": {
          "type": "string",
          "title": "Preferred Payment Option",
          "description": "Payment option ID from the offer, e.g. dmd_pow_native"
        },
        "controller_wallet_address": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Controller Wallet Address",
          "default": null,
          "description": "EVM wallet that will control the DID-LLM: 0x... (checksummed or all lower case) or eip155:<chain id>:0x.... Its control is proven like the key's, by signing a challenge (smart wallets included)."
        }
      }
    }
    arguments 127 lines
  • debitmydata_register_did unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_register_didArguments",
      "required": [
        "registration_intent_id"
      ],
      "properties": {
        "x402_payment": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "X402 Payment",
          "default": null,
          "description": "x402 quotes only: your signed PaymentPayload (x402 version 2) answering the payment requirements this tool returned. It may also be sent in the request's _meta['x402/payment']."
        },
        "registration_intent_id": {
          "type": "string",
          "title": "Registration Intent Id",
          "pattern": "^dmd_did_intent_[0-9A-HJKMNP-TV-Z]{26}$",
          "description": "registration_intent_id from the quote (dmd_did_intent_...)"
        }
      }
    }
    arguments 29 lines
  • debitmydata_list_in_directory unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_list_in_directoryArguments",
      "required": [
        "did"
      ],
      "properties": {
        "did": {
          "type": "string",
          "title": "Did",
          "pattern": "^(dmd_identity_[0-9A-HJKMNP-TV-Z]{26}|did:web:[^/?#\\s]{1,253}:agents:[0-9A-HJKMNP-TV-Z]{26})$",
          "description": "The DID-LLM (did:web:...:agents:...) or its identity ID (dmd_identity_...)"
        },
        "listed": {
          "type": "boolean",
          "title": "Listed",
          "default": true,
          "description": "false: remove the DID-LLM from the directory"
        },
        "profile": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "Profile",
          "default": null,
          "description": "When listing: entity_type (avatar, robot or sentient), specialty (3-120 characters), description (20-700 characters, 100 words at most); optional owner_name, region, country, created_on (YYYY-MM-DD). Public, plain text, no links."
        },
        "signature": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Signature",
          "default": null,
          "description": "Signature of the message, as for debitmydata_prove_wallet_control"
        },
        "challenge_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Challenge Id",
          "default": null,
          "description": "Leave empty to get the message to sign"
        },
        "controller_type": {
          "anyOf": [
            {
              "enum": [
                "ed25519",
                "eip155"
              ],
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Controller Type",
          "default": null,
          "description": "Who signs: ed25519 (the key, by default) or eip155 (the wallet)"
        }
      }
    }
    arguments 78 lines
  • debitmydata_list_supported_payment_options unknown never probed

    Approved assets, networks, wallet types and protocols currently enabled for a service, with the commercial fee.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_list_supported_payment_optionsArguments",
      "properties": {
        "service": {
          "type": "string",
          "title": "Service",
          "default": "did_registration",
          "description": "Service ID, e.g. did_registration"
        }
      }
    }
    arguments 12 lines
  • debitmydata_submit_payment_reference unknown never probed

    Report the transaction that pays a quote. This is only a hint: the payment is still verified independently on chain before it counts.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_submit_payment_referenceArguments",
      "required": [
        "payment_intent_id",
        "transaction_reference"
      ],
      "properties": {
        "payment_intent_id": {
          "type": "string",
          "title": "Payment Intent Id",
          "pattern": "^dmd_payment_intent_[0-9A-HJKMNP-TV-Z]{26}$",
          "description": "payment_intent_id from the quote (dmd_payment_intent_...)"
        },
        "transaction_reference": {
          "type": "string",
          "title": "Transaction Reference",
          "description": "Transaction ID / hash of the payment you broadcast"
        }
      }
    }
    arguments 21 lines
  • debitmydata_prove_wallet_control unknown never probed

    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).

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_prove_wallet_controlArguments",
      "required": [
        "registration_intent_id"
      ],
      "properties": {
        "signature": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Signature",
          "default": null,
          "description": "Signature of the challenge message: Ed25519 (base64url) for a key, or the wallet's personal_sign / signMessage result (0x...) for a wallet"
        },
        "challenge_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Challenge Id",
          "default": null,
          "description": "Leave empty to get a new challenge"
        },
        "controller_type": {
          "anyOf": [
            {
              "enum": [
                "ed25519",
                "eip155"
              ],
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Controller Type",
          "default": null,
          "description": "When getting a challenge: which controller to prove, ed25519 (the key) or eip155 (the wallet). By default the next one still to prove."
        },
        "registration_intent_id": {
          "type": "string",
          "title": "Registration Intent Id",
          "pattern": "^dmd_did_intent_[0-9A-HJKMNP-TV-Z]{26}$",
          "description": "registration_intent_id from the quote (dmd_did_intent_...)"
        }
      }
    }
    arguments 58 lines
  • debitmydata_verify_agent unknown never probed

    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).

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_verify_agentArguments",
      "required": [
        "did"
      ],
      "properties": {
        "did": {
          "type": "string",
          "title": "Did",
          "description": "The DID-LLM to verify (did:web:api.debitmydata.io:agents:...)"
        },
        "message": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Message",
          "default": null,
          "description": "The challenge message the agent signed"
        },
        "audience": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Audience",
          "default": null,
          "description": "Who verifies (your name or site), written in the challenge"
        },
        "signature": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Signature",
          "default": null,
          "description": "The agent's signature of the message (its key's, or its wallet's)"
        }
      }
    }
    arguments 53 lines
  • debitmydata_change_owner unknown never probed

    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 owners control the DID-LLM and sign-ins made before it end. With change_id alone: where it stands.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_change_ownerArguments",
      "required": [
        "did"
      ],
      "properties": {
        "did": {
          "type": "string",
          "title": "Did",
          "pattern": "^(dmd_identity_[0-9A-HJKMNP-TV-Z]{26}|did:web:[^/?#\\s]{1,253}:agents:[0-9A-HJKMNP-TV-Z]{26})$",
          "description": "The DID-LLM (did:web:...:agents:...) or its identity ID (dmd_identity_...)"
        },
        "change_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Change Id",
          "default": null,
          "description": "Leave empty to start a change; then the change_id it returned"
        },
        "signature": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Signature",
          "default": null,
          "description": "Its signature, as for debitmydata_prove_wallet_control"
        },
        "challenge_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Challenge Id",
          "default": null,
          "description": "The message you signed (from `messages`)"
        },
        "new_controller_network": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "New Controller Network",
          "default": null,
          "description": "The wallet's network, eip155:8453 (Base) by default"
        },
        "new_controller_public_key": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "New Controller Public Key",
          "default": null,
          "description": "The owner key after the change, ed25519:z6Mk...: the current one to keep it, a new one to replace it, or empty to have none"
        },
        "new_controller_wallet_address": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "New Controller Wallet Address",
          "default": null,
          "description": "The owner wallet after the change, 0x..., the same way"
        }
      }
    }
    arguments 93 lines
  • debitmydata_revoke_did unknown never probed

    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 change to).

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_revoke_didArguments",
      "required": [
        "did"
      ],
      "properties": {
        "did": {
          "type": "string",
          "title": "Did",
          "pattern": "^(dmd_identity_[0-9A-HJKMNP-TV-Z]{26}|did:web:[^/?#\\s]{1,253}:agents:[0-9A-HJKMNP-TV-Z]{26})$",
          "description": "The DID-LLM (did:web:...:agents:...) or its identity ID (dmd_identity_...)"
        },
        "reason": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Reason",
          "default": null,
          "description": "Optional, kept with the revocation"
        },
        "signature": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Signature",
          "default": null,
          "description": "Signature of the message, as for debitmydata_prove_wallet_control"
        },
        "challenge_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Challenge Id",
          "default": null,
          "description": "Leave empty to get the message to sign"
        },
        "controller_type": {
          "anyOf": [
            {
              "enum": [
                "ed25519",
                "eip155"
              ],
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Controller Type",
          "default": null,
          "description": "Who signs: ed25519 (the key, by default) or eip155 (the wallet)"
        }
      }
    }
    arguments 71 lines
  • debitmydata_get_purchase_quote unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_get_purchase_quoteArguments",
      "required": [
        "product_id"
      ],
      "properties": {
        "product_id": {
          "type": "string",
          "title": "Product Id",
          "description": "Product ID from debitmydata_catalog"
        }
      }
    }
    arguments 14 lines
  • debitmydata_purchase unknown never probed

    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 "settled", then debitmydata_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.

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_purchaseArguments",
      "required": [
        "product_id",
        "preferred_payment_option",
        "details"
      ],
      "properties": {
        "details": {
          "type": "object",
          "title": "Details",
          "description": "Product-specific fields. For did_registration: display_name, participant_type, controller_public_key and/or controller_wallet_address (with optional controller_network), and optionally metadata. For a donation (inference_donation): amount_usd, and optionally donor_name and donor_did. For an add-on (such as bottybotty_entry): did, the DID-LLM it is for",
          "additionalProperties": true
        },
        "product_id": {
          "type": "string",
          "title": "Product Id",
          "description": "Product ID from debitmydata_catalog"
        },
        "x402_payment": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "X402 Payment",
          "default": null,
          "description": "Donations only: your signed PaymentPayload (x402 version 2) answering the payment requirements this tool returned. It may also be sent in the request's _meta['x402/payment']."
        },
        "idempotency_key": {
          "anyOf": [
            {
              "type": "string",
              "pattern": "^[A-Za-z0-9._:-]{16,128}$"
            },
            {
              "type": "null"
            }
          ],
          "title": "Idempotency Key",
          "default": null,
          "description": "did_registration only: optional random key (16-128 characters) for safe retries"
        },
        "preferred_payment_option": {
          "type": "string",
          "title": "Preferred Payment Option",
          "description": "Payment option ID"
        }
      }
    }
    arguments 55 lines
  • debitmydata_whoami unknown never probed

    The DID-LLM this request is signed in as: its full DID (did, what Copy ID copies) and short ID (did_llm_id, the DID's suffix), name, participant type, status, entitlements, owner wallet (null: not linked), registration date and environment; the current session apart (session: status, access, end with timezone); internal IDs, keys and links in advanced. 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 code).

    mcp-tool

    {
      "type": "object",
      "title": "debitmydata_whoamiArguments",
      "properties": {}
    }
    arguments 5 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 363850cfffc18956.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/363850cfffc18956/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/363850cfffc18956/badge.svg)](https://brick.blue/agent/363850cfffc18956?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
618ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.