IMEI Luhn checksum
Call when an agent has an IMEI and needs the Luhn checksum result. Does not confirm the device. Unpaid calls return HTTP 402. Unknown input returns 404 and is not charged.
1 route settlement-verified · $0.002 USDC/request · 1 endpoint · Data · base network · x402 protocol
Verified routes
GET /imei· $0.002 · 2026-10-28 · receipt
Other routes are unverified.
Networks: Base (settlement-verified)
Discovery is free. Agents search the catalogue here. Payment happens on the listing 402, not on PayAPI.
url https://payapi.market/mcpListing facts
- Provider
- agentshield.live
- Hosted at
agentshield.live- Category
- Data
- Price
- $0.002 USDC per request
- Payment networks
- Base
- Settlement-verified
- 1 route, last checked 2026-10-28
- Listed on PayAPI Market
- 2026-10-28
Try IMEI Luhn checksum
Call a verified route without paying first. The server should answer HTTP 402 Payment Required with the price, the USDC asset, the network and the wallet to pay. An x402 client pays that amount on Base and retries with the payment header.
curl -i "https://agentshield.live/imei?code=490154203237518"About this API
IMEI Luhn checksum is listed in the Data category with pricing at $0.002 USDC/request. One route has been settlement-verified by PayAPI Market on 2026-10-28. View receipt on Basescan.
Payments settle on base in USDC via the x402 protocol. AI agents discover this API through the PayAPI Market MCP server and pay per request without API keys or accounts.
This API exposes 1 endpoint.
Questions about this API
What does IMEI Luhn checksum do?
Call when an agent has an IMEI and needs the Luhn checksum result. Does not confirm the device. Unpaid calls return HTTP 402. Unknown input returns 404 and is not charged. It is provided by agentshield.live.
How much does IMEI Luhn checksum cost?
IMEI Luhn checksum is priced at $0.002 USDC per request, paid per call with no subscription. PayAPI Market paid 0.002 USDC for one call to /imei when it verified the listing. The exact amount for each call is in the HTTP 402 response before any money moves.
Do I need an API key or account to use IMEI Luhn checksum?
No. IMEI Luhn checksum uses the x402 protocol, so an agent pays per request in USDC on Base and gets the response, with no API key, account or signup.
Has IMEI Luhn checksum been verified?
Yes, 1 route. PayAPI Market paid for a real call from its own wallet, received real data back and recorded the USDC settlement on-chain, most recently on 2026-10-28.
How does an AI agent find IMEI Luhn checksum?
Through the free PayAPI Market MCP server at https://payapi.market/mcp, using search_apis or get_api, or over plain HTTP at https://payapi.market/agent/search. Discovery is free; the agent pays the provider directly on the listing's own 402.
More Data APIs · Browse the marketplace · List your own API
Related APIs
- ABA routing checksum · 1 route verified · Call when an agent has a US ABA routing number and needs the checksum result. Does not confirm the bank or an account. Unpaid calls return HTTP 402. Unknown input returns 404 and is not charged.
- SEDOL checksum · 1 route verified · Call when an agent has a SEDOL and needs the checksum result. Does not confirm the security or a price. Unpaid calls return HTTP 402. Unknown input returns 404 and is not charged.
- CUSIP checksum · 1 route verified · Call when an agent has a CUSIP and needs the checksum result. Does not confirm the security or a price. Unpaid calls return HTTP 402. Unknown input returns 404 and is not charged.
- ISO 6346 container check digit · 1 route verified · Call when an agent has a shipping container number and needs the ISO 6346 check digit. Does not confirm the container. Unpaid calls return HTTP 402. Unknown input returns 404 and is not charged.
- Telephone country calling code · 1 route verified · Call when an agent needs the telephone country calling code for a country. Not a phone-number lookup. Unpaid calls return HTTP 402. Unknown input returns 404 and is not charged.
- LEI checksum · 1 route verified · Call when an agent has an LEI and needs the checksum result. Does not confirm the legal entity. Unpaid calls return HTTP 402. Unknown input returns 404 and is not charged.