# Lordevo Shop > Lordevo Shop sells 48 website, DNS, email, domain and data checks and five larger SEO and security services to AI agents, paid per call in USDC on Base with x402, over an HTTP API and a remote MCP server. - Canonical: https://www.anchorterminal.com/tools/lordevo-shop - Pricing: https://www.anchorterminal.com/tools/lordevo-shop#pricing - Reviews: https://www.anchorterminal.com/tools/lordevo-shop#reviews - Markdown: https://www.anchorterminal.com/tools/lordevo-shop.md (~10,350 tokens) - Slim: https://www.anchorterminal.com/tools/lordevo-shop.min.md (~2,630 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/lordevo-shop.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-10-30 ## Overview **Grade B · 65.6/100 · rank #360 of 1226 · #1 in SEO & search visibility · not agent-ready · confidence medium** ## Assessment Every endpoint takes x402 in USDC on Base with no account, prices from $0.002 are published in llms.txt, catalog.json and an OpenAPI 3.1 file, and failed calls aren't charged. The shop went live on 22 October 2026, its status page covers under a day of its own logs, no legal entity is named, and the terms are Lordevo SEO's. ## Facts | Field | Value | | --- | --- | | Vendor | Lordevo (https://lordevo.com) | | Kind | HTTP API | | Category | SEO & search visibility (https://www.anchorterminal.com/categories/seo) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://shop.lordevo.com` | | Auth | None · No account, API key or signup. Payment is the credential. The first call answers HTTP 402 with x402 v2 terms in a PAYMENT-REQUIRED header and v1 terms in the JSON body; the client signs a USDC authorisation on Base (eip155:8453) and retries with PAYMENT-SIGNATURE (v2) or X-PAYMENT (v1). Over MCP the tool result carries the payment requirement and the client retries with `_meta["x402/payment"]`. The free trial needs neither a wallet nor a key, only `trial=1` in the query, the `X-Lordevo-Trial: 1` header or `"trial": true` in MCP arguments. The Deep security check also needs a free domain verification by DNS TXT record or a well-known file, and the SEO services an attestation of ownership in the request body. | | Pricing | Pay per use ($0.02 / call) · Per call in USDC on Base over x402, with no plan or minimum. 48 quick checks at $0.002 (24 tools), $0.005 (12), $0.01 (7) and $0.02 (5), the weekly digest at $0.002, and five services at $1 (passive security check), $2 (SEO audit of up to 10 pages), $3 (content plan or site fix plan) and $5 (article or deep security scan). Failed, refused, busy or unverified calls aren't charged. 3 free calls per IP per UTC day on tools priced up to $0.005 with `trial=1` (36 of the 48 tools). Discovery files, MCP initialize, tools/list, list_services and get_sample_output, and A2A message/send are free. Quick-check prices were cut twice on 29 October 2026 (https://shop.lordevo.com/changelog, checked 2026-10-30). | | x402 | Accepted · from $0.02/call · x402 v2 and v1 on every paid endpoint, exact scheme, USDC on Base (eip155:8453), settled through Coinbase CDP per llms.txt. The manifest at https://shop.lordevo.com/.well-known/x402.json lists 64 resources with `accepts[]` (amount in USDC base units, payTo 0x0876A79Bb5A88Bf338E6b47b4530359527b01d73, maxTimeoutSeconds 120), and the OpenAPI file carries `x-price-usd` and `x-payment-info` per operation. Coinbase's x402 Bazaar lists 45 resources for that payTo address (https://api.cdp.coinbase.com/platform/v2/x402/discovery/merchant?payTo=0x0876A79Bb5A88Bf338E6b47b4530359527b01d73, read 2026-10-30). We didn't probe the 402; the 30 October listing check's trial GET answered 200 with `x-lordevo-trial-remaining: 2`. | | Licence | Proprietary hosted service with no terms page of its own; the site footer links to Lordevo SEO's terms (22 October 2026) and privacy policy (24 October 2026). The lordevo-x402 client on npm is MIT | | Tools exposed | 50 | | Packages | npm: `lordevo-x402`; pypi: `lordevo-x402`; npm: `elizaos-plugin-lordevo` | | MCP registry name | `com.lordevo/shop` | | Docs | https://shop.lordevo.com/llms.txt | | llms.txt | https://shop.lordevo.com/llms.txt | | Last release | 2026-10-30 | | Surface listed | The HTTP API at shop.lordevo.com paid with x402, with the MCP server at /mcp and the A2A router at /a2a described. Read from llms.txt, /start, openapi.json, catalog.json, examples.json, the well-known files, the status and changelog pages, lordevo.com, seo.lordevo.com and pentest.lordevo.com on 30 October 2026. No MCP session was opened, no call was made and nothing was paid | | How new | Changelog entries from 22 October 2026 (shop live) to 30 October 2026. lordevo.com was registered on 1 May 2021 and the Wayback Machine has no copy of shop.lordevo.com | | Quick checks | 48 GET endpoints under /api/quick in four groups. Fetch and read the web (10, page Markdown and metadata, RAG chunks, feeds, PDF text, page diffs, sitemaps, link previews, readability), web and domain checks (15, link and redirect checks, DNS, TLS, RDAP, IP owner, email validation and authentication, CORS, HTTP ping, lookalike domains, tech stack), data utilities (11, JSON Schema validation and repair, token estimates, time zones, cron, URL cleaning, maths, dates, regex, text diff, MYR rates) and SEO, security and site verdicts (12) | | Services | POST endpoints under /api/svc. SEO audit of up to 10 pages $2, passive website security check $1, deep active scan $5 (verified hosts only), content plan $3, article $5, site fix plan $3. Long jobs answer 202 with a result_url; results and private HTML reports expire after 30 days | | Payment | x402 exact scheme, USDC on Base mainnet, v2 (PAYMENT-REQUIRED and PAYMENT-SIGNATURE headers) and v1 (JSON body and X-PAYMENT). Settled through Coinbase CDP per llms.txt. payTo 0x0876A79Bb5A88Bf338E6b47b4530359527b01d73, maxTimeoutSeconds 120 on quick checks | | Trial | 3 calls per IP per UTC day on tools priced up to $0.005, with `trial=1`, `X-Lordevo-Trial: 1` or `"trial": true` over MCP. Failed calls don't count. The listing check's trial call on 30 October 2026 returned `x-lordevo-trial-remaining: 2` | | MCP server | Streamable HTTP with JSON responses at https://shop.lordevo.com/mcp. 50 tools per the server card and the listing check's tools/list, the 48 quick checks plus the free list_services and get_sample_output. No toolsets. Registry entry com.lordevo/shop 1.1.1 of 27 October 2026 | | A2A | JSON-RPC at /a2a, protocol 0.3.0, with an agent card at /.well-known/agent-card.json. message/send is free and answers with the endpoint, price and payment terms for a named skill | | Errors and charging | 400 bad input, 403 robots.txt or authorisation refused, 422 target unusable, 429 busy, 503 at capacity with Retry-After, all not charged. 402 carries the price. Any status of 400 or above after a payment leaves it unsettled with `charged: false`. A known issue shows a Cloudflare 520 instead of a JSON 400 for a malformed percent escape | | Limits and caching | Per tool, for example 10 URLs on links-batch, 40 links on broken-links, 1,000 URLs on sitemap-urls, 60,000 characters on page-markdown, 10 MB and 50 pages on pdf-text, 400,000 characters on text inputs. Results cached from 2 minutes (DNS) to 24 hours (RDAP) by tool; http-ping and page-diff never. No rate limit numbers for paid calls | | Status | https://shop.lordevo.com/status and /status.json, rebuilt every 10 minutes from the shop's own request log, which starts on 29 October 2026 12:57 UTC. 24-hour and 7-day windows with request outcomes, 402 and answer latency, settled payments, process starts, tunnel restarts and unlogged gaps of 10 minutes or more | | Legal | No entity named. shop.lordevo.com/terms and /privacy answer 404, lordevo.com/terms and /privacy answer 404, and the footer links go to seo.lordevo.com/terms (22 October 2026) and /privacy (24 October 2026). Liability is limited to the amount paid. hello@lordevo.com for everything | | Data handling | Lordevo SEO's privacy policy says IP addresses are kept in memory for an hour for rate limiting, no cookies or third-party analytics, Cloudflare carries traffic, and page text for content plans goes to Anthropic's Claude, OpenAI's Codex or a local model. The shop's AI verdict tools say they run on a local model. Nothing read covers wallet addresses or the shop's request log | | Clients | lordevo-x402 0.1.3 on npm (MIT, Node 20.10 or later, peer dependencies viem, @x402/evm and @x402/fetch) and on PyPI with LangChain and CrewAI tools, both 29 October 2026, and elizaos-plugin-lordevo 0.1.1 on npm (27 October). No source repository found | | Directory listings | Coinbase x402 Bazaar (45 resources for the payTo address, read 30 October 2026), PayAPI Market (listed 26 October 2026, one route settlement-verified) and mcp.tc. mcpservers.org sits behind a bot check and wasn't read | | Capabilities | web.fetch, web.extract, email.verification, pdf.extract | | Tags | hosted, official, closed-source, x402, no-key, no-card, free-trial, usage-priced, openapi, llms-txt, mcp, mcp-registry, typescript, python, async-jobs, status-page, new | | JSON | https://www.anchorterminal.com/api/v1/tools/lordevo-shop.json | ## Score breakdown (methodology v0.7, October 2026 research run) Assessed 2026-10-30 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 48 | 9.6 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 80 | 13.0 | | Agent ergonomics | 13% | 16.2 | 67 | 10.9 | | Security & auth | 14% | 17.5 | 45 | 7.9 | | Payments & pricing | 10% | 12.5 | 98 | 12.2 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 76 | 6.7 | | Transparency & trust (editorial 34, provenance 87) | 7% | 8.8 | 61 | 5.3 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **65.6 → B** | ### Why each score - Reliability 48 (checked 2026-10-30): Hosted reading, scored on the HTTP API at shop.lordevo.com. The status page at shop.lordevo.com/status is the vendor's own, rebuilt every 10 minutes from the shop's request log with a JSON twin, but it has no components and the log starts on 29 October 2026 at 12:57 UTC (12 of 20). The record is under a day long. It shows 0 server errors in 15,871 logged requests, 6 process starts and 7 tunnel restarts in 24 hours, one unlogged gap of 12 minutes, and a known issue that an outside registry measured low 30-day uptime on the A2A endpoint, which the vendor traces to tunnel drops. Eight days of operation and no outage of the paid API recorded, but restarts and drops the vendor itself reports (10 of 30). No rate limit numbers for paid calls were found; the only figure is the trial cap of 3 calls per IP per UTC day (3 of 15). 429 and 503 answer with Retry-After and are not charged, the OpenAPI file documents 503 on 63 operations and 429 on the 6 services, every quick check is a read, and a failed call after payment leaves the payment unsettled, so retries are safe. No backoff guidance beyond waiting the given seconds (13 of 15). No SLA. llms.txt says no ranking, traffic or security outcome is promised (0). No beta or preview label; the catalog marks every service on sale and backend ready (10). 12 + 10 + 3 + 13 + 0 + 10 = 48. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 80 (checked 2026-10-30): An OpenAPI 3.1.0 file (version 1.9.0) with 62 paths and 71 operations, a 200 response schema and example on every quick check, and `x-price-usd` and `x-payment-info` per operation. It declares no security scheme, which fits a keyless x402 API, and catalog.json adds a JSON Schema input per quick check with `additionalProperties: false`. The MCP server card lists the 50 tools without input schemas and we didn't open a session (23 of 25). llms.txt, a Markdown /start page, catalog.json and examples.json (10). Every description says what the tool does, its limits, cache time and typical latency, and some say what it doesn't do (can-fetch never downloads the body, email-validate does no SMTP probing, ip-info has no geolocation or ASN). The LITE tiers name their full versions. Little guidance on choosing between link-check, http-ping and redirect-chain, and no 'not for' lines (13 of 20). 83 query parameters with 75 required markers and 10 enums, service bodies typed with `const: true` and `minLength`, and only the /mcp and /a2a envelopes free-form. The `trial` parameter and `X-Lordevo-Trial` header appear in llms.txt and /start but in none of the 71 operations (11 of 15). 66 parameter examples and a 200 example per quick check, and 400, 402, 403, 422, 429 and 503 documented with their charging on 63 operations, but error bodies have no schema and the 402 shape is described only in prose (12 of 15). OpenAPI version 1.9.0, a dated changelog from 22 to 30 October 2026 with a JSON twin and an unreleased section, no versioned paths and no deprecation notice period (11 of 15). 23 + 10 + 13 + 11 + 12 + 11 = 80. - Agent ergonomics 67 (checked 2026-10-30): API reading of the checklist. Responses are single JSON objects with some size controls (`type` on dns-lookup, `limit` 1 to 100 on feed-parse, `max_pages`, `max_tokens`, `count`, `max_matches`) and hard caps per tool such as 60,000 characters on page-markdown, with no field selection. The MCP server would score 5 of 25 on its 50 tools with no toolsets, and its card alone runs to about 32,800 characters of names, titles and descriptions (15 of 25). No pagination, since every call is one shot; per-tool limits of 10 URLs, 40 links, 1,000 sitemap URLs, and a `type` filter on DNS (10 of 20). JSON error bodies with `charged: false`, documented meanings for 400, 402, 403, 422, 429 and 503, and 404 bodies in JSON since 30 October, but no error schema and a known issue where a malformed percent escape shows a Cloudflare 520 (14 of 20). All 48 quick checks are reads, failed calls are never charged, results are cached from 2 minutes to 24 hours by tool, and the npm client caches identical calls locally; no idempotency key on the paid POST services, and readOnlyHint or destructiveHint annotations weren't read (13 of 20). One required parameter per quick check with defaults for the rest, official clients on npm and PyPI plus an elizaOS plugin, and a `maxPriceUsd` cap in the client that defaults to $0.05 (15). 15 + 10 + 14 + 13 + 15 = 67. - Security & auth 45 (checked 2026-10-30): No credential exists. Each call carries a signed USDC authorisation for one amount on Base, in a PAYMENT-SIGNATURE or X-PAYMENT header, never in the query string; `trial=1` is a flag, not a secret. The wallet key stays with the agent and nothing can be revoked server side, so the scope is per call but a leaked wallet key is total (20 of 30). Every quick check reads public data, the site fix plan writes nothing to the site, the SEO services need an ownership attestation, and the deep active scan is refused with 403 before any 402 unless the host passed a free DNS TXT or well-known verification. The attestation is self-declared and no tool annotations were read (17 of 20). page-markdown, page-meta, pdf-text, feed-parse, link-preview and the verdict tools return third-party page content, and no prompt-injection guidance was found in llms.txt, the OpenAPI file, the catalog or the client README (2 of 15). Each answer carries `charged`, the trial answer carries `x-lordevo-trial-remaining`, and payments settle on chain where the payer can see them, but with no account there is no per-call log for the operator beyond the aggregate status page (6 of 15). No security.txt on shop.lordevo.com, lordevo.com, seo.lordevo.com or pentest.lordevo.com, no disclosure policy, bug bounty, SOC 2 or ISO 27001, and no advisories (0 of 20). 20 + 17 + 2 + 6 + 0 = 45. - Payments & pricing 98 (checked 2026-10-30): x402 on every paid endpoint, v2 and v1, USDC on Base (eip155:8453), exact scheme, with a manifest of 64 resources at /.well-known/x402.json and 45 of them in Coinbase's x402 Bazaar under the payTo address. We didn't probe the 402; the 30 October listing check's trial call answered 200 (40). Per-call prices for all 48 quick checks, the digest and the 7 service tiers are published in llms.txt, catalog.json, the OpenAPI file and the manifest, $0.002 to $5 (20). 3 free calls per IP per UTC day on tools priced up to $0.005 with no wallet or card, covering 36 of 48 tools, plus free discovery and sample outputs. Two points withheld because the trial is small and skips the $0.01 and $0.02 tools (18 of 20). No signup of any kind; an agent with a funded Base wallet calls and pays (20). 40 + 20 + 18 + 20 = 98. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 76 (checked 2026-10-30): The newest changes are the four data utilities, the reliability fixes and the status page, all dated 30 October 2026, with OpenAPI version 1.9.0 (30). Nine dated changelog entries between 22 and 30 October 2026, npm releases 0.1.0 to 0.1.3 between 27 and 29 October, and registry versions 1.0.0, 1.1.0 and 1.1.1 (20). Closed service with a public changelog, an unreleased section and support by email to hello@lordevo.com, which the about page says a human owner answers. No community channel, and the GitHub repository the registry entry names, forbot26/lordevo-x402, answers 404 on the web and the API, as does the user page (7 of 15). In the official MCP registry as com.lordevo/shop under the vendor's domain, with current clients on npm and PyPI (15). The npm package is MIT with Node 20.10 or later, optional peer dependencies on viem and @x402, a `node --test` script and no repository field; no CI is visible because no source repository was found, and the PyPI project page sits behind a bot check so only its release feed was read (4 of 10). 30 + 20 + 7 + 15 + 4 = 76. - Transparency & trust 61 (checked 2026-10-30): Closed service with no terms of its own. shop.lordevo.com/terms and lordevo.com/terms answer 404 and the footer links go to Lordevo SEO's terms of 22 October 2026, which cover scans, Stripe orders and refunds and limit liability to the amount paid, without mentioning the shop, x402 or wallets. No legal entity, registration number or address on any page read. The npm client is MIT (10 of 30). Lordevo SEO's privacy policy of 24 October 2026 is specific where it applies (IP addresses in memory for an hour, no cookies or third-party analytics, page text for content plans sent to Anthropic's Claude, OpenAI's Codex or a local model, encrypted CMS credentials), but it doesn't cover the shop's request log, wallet addresses or settlement through Coinbase CDP, and the shop's statements that its verdict tools use a local model and that report links expire after 30 days sit in llms.txt rather than a policy (12 of 30). No deprecation policy or notice period; the changelog dates two reprices in one day and an unreleased section (4 of 20). Cloudflare, Stripe, Google, Anthropic and OpenAI are named as processors in the privacy policy and Coinbase CDP as the settlement facilitator in llms.txt, with http-ping measured from Malaysia and no data location stated for the shop (8 of 20). 10 + 12 + 4 + 8 = 34. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (21 items): https://www.anchorterminal.com/fixes/lordevo-shop.md (JSON https://www.anchorterminal.com/fixes/lordevo-shop.json) ### What we couldn't check - unchecked: the MCP server's live tools/list, its input schemas and any readOnlyHint or destructiveHint annotations. We opened no session; the 50-tool count is from the server card and the 30 October listing check, and the card lists no schemas. - unchecked: the 402 challenge itself. We made no call; the 30 October listing check's trial GET to dns-lookup answered 200 in under a second with `x-lordevo-trial-remaining: 2`, and the vendor's /start page says the examples were verified on 29 October. - unchecked: the legal entity. No page on lordevo.com, shop.lordevo.com, seo.lordevo.com or pentest.lordevo.com names a company, registration number or address; the about page says a small, independent online service with a human owner, and the submitter wrote Lordevo Team, Malaysia. - unchecked: the PyPI project page, which sits behind a bot check. The package's publisher, licence and README on PyPI come only from the release feed (author hello@lordevo.com, four releases from 27 to 29 October 2026). - unchecked: mcpservers.org, which answers with a bot check, so that listing stays the vendor's claim. PayAPI Market (listed 26 October 2026, 13 endpoints, one route verified) and mcp.tc were read; both are stale against the current 48 tools. - unchecked: npm and PyPI weekly downloads, GitHub stars. The registry entry names github.com/forbot26/lordevo-x402 as the source, and the repository, the user page and the API all answer 404, so no source, CI, issues or stars could be read. - The terms and privacy pages that lordevo.com/terms and /privacy were expected to draw by script answer 404; the readable terms and privacy policy are at seo.lordevo.com/terms (22 October 2026) and seo.lordevo.com/privacy (24 October 2026), written for Lordevo SEO. pentest.lordevo.com/terms (25 October 2026) covers Lordevo Security. None covers the shop, x402 or wallet data. - Settlement through Coinbase CDP is the vendor's statement in llms.txt. The Bazaar lists the shop's resources, which is consistent with the CDP facilitator having seen them, but the facilitator URL isn't in the manifest. - The status page's 7-day window covers only the 20 hours since the request log began, and its restart lists reach back to 23 and 24 October. Whether the tunnel drops it reports touched paid calls can't be told from it. - Descriptions on third-party listings and in the registry are stale. The registry's 1.1.1 entry says 33 paid checks from $0.01, the npm description says 44 tools, and the catalog has 48 at $0.002 and up after the 29 and 30 October changes. Recorded, not deducted. - Category fit. Lordevo returns no keywords, search volumes, backlinks, rankings or traffic, so the seo category's capabilities don't apply; the listing uses web.fetch, web.extract, email.verification and pdf.extract. It sits in seo because its own framing is SEO and website security and no category covers website trust, DNS, email and security-header checks. - Lordevo Shop doesn't do LocalGhost's or letme's job. Its agent-readiness score grades websites, not MCP servers, and it holds no credentials for anyone. Lordevo SEO's privacy policy names Anthropic's Claude, whose models wrote this grade, as one of the models that writes its content plans; no score depends on that. ### Sources - llms.txt (tools, prices, services, payment rules): (seen 2026-10-30) - start page with curl, JavaScript, Python and MCP examples: (seen 2026-10-30) - OpenAPI 3.1 file, version 1.9.0: (seen 2026-10-30) - catalog.json with input schemas and prices: (seen 2026-10-30) - examples.json: (seen 2026-10-30) - services.json: (seen 2026-10-30) - x402 resources list: (seen 2026-10-30) - x402 manifest with accepts per endpoint: (seen 2026-10-30) - MCP server card (50 tools): (seen 2026-10-30) - A2A agent card: (seen 2026-10-30) - status page: (seen 2026-10-30) - status JSON: (seen 2026-10-30) - changelog: (seen 2026-10-30) - changelog JSON: (seen 2026-10-30) - shop home page: (seen 2026-10-30) - robots.txt (shop): (seen 2026-10-30) - about page: (seen 2026-10-30) - agents page: (seen 2026-10-30) - press kit: (seen 2026-10-30) - directory llms.txt: (seen 2026-10-30) - terms (Lordevo SEO): (seen 2026-10-30) - privacy policy (Lordevo SEO): (seen 2026-10-30) - terms (Lordevo Security): (seen 2026-10-30) - official MCP registry search: (seen 2026-10-30) - npm lordevo-x402, full document with release times and README: (seen 2026-10-30) - npm elizaos-plugin-lordevo: (seen 2026-10-30) - PyPI release feed for lordevo-x402: (seen 2026-10-30) - x402 Bazaar resources for the payTo address: (seen 2026-10-30) - PayAPI Market listing: (seen 2026-10-30) - RDAP for lordevo.com: (seen 2026-10-30) - Wayback availability for shop.lordevo.com: (seen 2026-10-30) ## Score history Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/lordevo-shop/history.json - 2026-10-30: graded 65.6 B (methodology 0.7) ## Who's behind it (provenance 87/100, checked 2026-10-30) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Lordevo (no legal entity named) | 20/20 | | Domain age | lordevo.com, registered 2021-05-01 (5 years) | 11/15 | | Endpoint on the vendor's domain | shop.lordevo.com | 15/15 | | Terms of service | published | 10/10 | | Privacy policy | published | 10/10 | | Status page | shop.lordevo.com/status | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | | People named | not researched yet | n/a | | Support route | a support address, help pages | 5/5 | No page read names a company, registration number or address. lordevo.com/about describes a small, independent online service with a human owner who answers every email, prices in Malaysian ringgit, euros or US dollars by the visitor's country, and http-ping is measured from Malaysia. The npm package's author is Lordevo with hello@lordevo.com and its publisher is forbot26. shop.lordevo.com/terms and /privacy answer a JSON 404, and lordevo.com/terms and /privacy answer an HTML 404. The footer links of lordevo.com point to seo.lordevo.com/terms (last updated 22 October 2026) and seo.lordevo.com/privacy (24 October 2026), written for Lordevo SEO. pentest.lordevo.com/terms (25 October 2026) covers Lordevo Security. None mentions the shop, x402 or wallets. The API, MCP server, A2A endpoint and discovery files all answer on shop.lordevo.com, a subdomain of the vendor's domain, behind Cloudflare. The status page reports tunnel restarts, so the origin reaches Cloudflare through a tunnel. The status page at shop.lordevo.com/status is the vendor's own, generated from its request log every 10 minutes, with a JSON twin at /status.json. The changelog at /changelog has a JSON twin at /changelog.json. /.well-known/security.txt answers 404 on shop.lordevo.com (JSON), lordevo.com, seo.lordevo.com and pentest.lordevo.com. RDAP for lordevo.com gives a registration date of 2021-05-01, registrar NameCheap, Inc., and a last change on 2026-10-22, the day the changelog says the shop went live. firstReleased is the changelog's 'Shop live' entry of 22 October 2026. The npm package was created on 27 October 2026 and the Wayback Machine has no copy of shop.lordevo.com; its earliest copy of lordevo.com is 12 July 2025. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://seo.lordevo.com/terms), not read yet. **Privacy policy** (https://seo.lordevo.com/privacy), not read yet. ## Humans behind the project (researched 2026-10-30 from public pages, not part of the grade) ### Key people - No people named yet. - Note: no person is named on any lordevo page read on 30 october 2026. lordevo.com/about says a small, independent online service with a human owner who runs the service, oversees the automated work and answers every email; seo.lordevo.com/contact and the terms repeat that it is run by a human owner. the press kit, the agents page, the shop's llms.txt, the a2a agent card (provider lordevo), the mcp registry entries and the npm package (author lordevo, publisher forbot26) give no name. the github user and repository the registry names (forbot26/lordevo-x402) answer 404. the form submission said lordevo team, malaysia. no linkedin, x or github link appears on the pages, and none was searched for. investors were looked for on lordevo.com, its about and press pages, the blog's sitemap, the shop's changelog and the terms; nothing mentions funding, and no legal entity is named, so ownership is unknown. ### Getting support - Support email: hello@lordevo.com - Help: https://shop.lordevo.com/llms.txt - Help: https://shop.lordevo.com/start - Help: https://shop.lordevo.com/status - Sources: https://lordevo.com/about, https://lordevo.com/press, https://lordevo.com/agents, https://seo.lordevo.com/contact, https://seo.lordevo.com/terms, https://pentest.lordevo.com/terms, https://shop.lordevo.com/llms.txt, https://shop.lordevo.com/.well-known/agent-card.json, https://shop.lordevo.com/changelog, https://blog.lordevo.com/sitemap.xml, https://registry.modelcontextprotocol.io/v0/servers?search=lordevo, https://registry.npmjs.org/lordevo-x402 ## Live (updated 2026-10-30 13:20 UTC) - Right now: up, HTTP 200, 1 s, checked 2026-10-30 13:20 UTC (get on `https://shop.lordevo.com`) - Uptime 24h 100.0% (17 probes) · 30 days 100.0% (17 probes) · p50 1.4 s · p95 4.4 s - Vendor status page: unknown, no machine-readable status found - Always current: https://www.anchorterminal.com/api/v1/live/lordevo-shop.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Site check bundle (`site-check`) | $0.02 | per call | Also agent-readiness, site-snapshot, seo-audit-lite and security-scan-lite | | Lookups and checks (`dns-lookup`, `url-trust`, `link-check`, `ssl-cert`, `email-validate`, 19 more) | $0.002 | per call | 24 tools at this price, repriced on 29 October 2026 | | Page readers and graded checks (`page-markdown`, `security-headers`, `email-auth`, 9 more) | $0.005 | per call | 12 tools, the dearest tier the free trial covers | | On-page SEO check (`seo-page`) | $0.01 | per call | Also tech-stack, links-batch, broken-links, pdf-text, verdict-card and site-verdict | | SEO audit, up to 10 pages | $2 | per call | POST /api/svc/seo-audit/standard with an ownership attestation | | Website security check, passive | $1 | per call | Any public site. The deep active scan is $5 and needs a verified host | | SEO article | $5 | per call | Content plan and site fix plan are $3 each. 202 and poll | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - x402 v1 and v2 on all 64 paid resources, USDC on Base, with a 3-call daily trial that needs no wallet and free discovery, tools/list and sample outputs - Per-call prices from $0.002 to $5 published in llms.txt, catalog.json, the OpenAPI file and the x402 manifest, and 400, 403, 422, 429 and 503 answers are not charged - An OpenAPI 3.1 file of 71 operations with a 200 example per quick check, typed inputs in catalog.json, and official clients on npm and PyPI - Every quick check reads public data, and the active Deep security scan is refused with 403 before any 402 unless the host passed a free DNS or well-known verification - A public status page and changelog, both with JSON twins, rebuilt from the shop's own logs every 10 minutes ## Weaknesses - Eight days old on 30 October 2026, with a request log that starts on 29 October, 6 process starts and 7 tunnel restarts in 24 hours, and a self-reported uptime problem on the A2A endpoint - No terms or privacy policy for the shop itself; the footer links to Lordevo SEO's, which don't mention x402, wallets or the shop's request log, and no legal entity is named on any page read - No rate limit numbers for paid calls, only 429 or 503 with Retry-After, and no SLA - No security.txt on shop.lordevo.com, lordevo.com, seo.lordevo.com or pentest.lordevo.com, and no disclosure policy or bug bounty - The MCP server lists 50 tools with no toolsets, and the registry entry names a GitHub repository (forbot26/lordevo-x402) that answers 404 - Doesn't cover the seo category's keyword, backlink, ranking or traffic data; the SEO tools are on-page and technical checks ## Before you call it (notes for agents) 1. Start with GET /api/quick/site-check?url=... ($0.02) or a $0.002 tool with `trial=1`; the trial allows 3 calls per IP per UTC day on tools priced up to $0.005 and answers 402 once used up. 2. Use an x402 v2 client (@x402/fetch with ExactEvmScheme, or x402[httpx,evm] in Python) on Base mainnet; the 402 carries v2 terms in PAYMENT-REQUIRED and v1 terms in the body. 3. Treat 429 and 503 as a wait for the Retry-After seconds, never as a billing event; any status of 400 or above after a payment leaves the payment unsettled and the body says `charged: false`. 4. For the services under /api/svc, send `url` and `authorization` with `attested: true` and a statement of at least 10 characters; the Deep scan also needs `verification.key` from the free /verify step, and long jobs answer 202 with a result_url to poll every 30 to 60 seconds. 5. Over MCP, pass `"trial": true` in the arguments for a free call; a paid call returns the payment requirement as the tool result, then retry with `params._meta["x402/payment"]`. 6. Set `maxPriceUsd` in the lordevo-x402 client (default $0.05) and keep result_url and verification_key private; report links expire after 30 days. ## Connect Install: ```bash npm i lordevo-x402 @x402/fetch @x402/evm viem ``` First request: ```bash curl -i "https://shop.lordevo.com/api/quick/dns-lookup?host=example.com&trial=1" ``` Claude Code: ```bash claude mcp add --transport http lordevo-shop https://shop.lordevo.com/mcp ``` MCP client configuration: ```json { "mcpServers": { "lordevo-shop": { "url": "https://shop.lordevo.com/mcp" } } } ``` Through letme: https://letme.dev/lordevo-shop. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Firecrawl MCP | A | 78 | 22 | web.fetch, web.extract | no | https://www.anchorterminal.com/tools/firecrawl-mcp.md | | Tavily API + MCP | BB | 77 | 36 | web.extract, web.fetch | no | https://www.anchorterminal.com/tools/tavily-mcp.md | | You.com APIs | BB | 75.9 | 48 | web.fetch, web.extract | no | https://www.anchorterminal.com/tools/you-com-api.md | | Spider | BB | 75.4 | 57 | web.extract, web.fetch | yes | https://www.anchorterminal.com/tools/spider-cloud.md | | Parallel Search and Task APIs | BB | 75.1 | 63 | web.fetch, web.extract | no | https://www.anchorterminal.com/tools/parallel-search-api.md | | Scrapfly | B | 69.6 | 201 | web.fetch, web.extract | no | https://www.anchorterminal.com/tools/scrapfly.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The shop went live on Base mainnet on 22 October 2026, the quick checks and MCP server followed on 26 October, and the changelog records nine dated entries to 30 October (source: ) - An OpenAPI 3.1.0 file (version 1.9.0) with 62 paths and 71 operations carries a price, a 200 example and 400, 402, 403, 422 and 503 responses marked not charged on every quick check (source: ) - catalog.json carries a JSON Schema input per quick check with `additionalProperties: false`, and the 50-tool MCP server at /mcp mirrors them with two free tools, list_services and get_sample_output (source: ) - The status page is built from the shop's own request log every 10 minutes, with 0 server errors in 15,871 requests, 6 process starts and 7 tunnel restarts in 24 hours, and a known issue that an outside registry measured low 30-day uptime on the A2A endpoint (source: ) - The official MCP registry lists com.lordevo/shop 1.0.0 (26 October 2026), 1.1.0 and 1.1.1 (27 October), all with the remote https://shop.lordevo.com/mcp (source: ) - lordevo-x402 0.1.3 on npm (MIT, publisher forbot26, author Lordevo) and PyPI, both released 29 October 2026, wrap the quick checks with a `maxPriceUsd` cap that defaults to $0.05 (source: ) - Three verdict tools (page-quality, site-verdict, verdict-card) run on what Lordevo calls its own local model with no cloud AI, and verdict cards get a permanent public URL (source: ) - No legal entity is named. The about page describes a small independent service with a human owner, prices in Malaysian ringgit, euros or US dollars, and http-ping is measured from Malaysia (source: ) - #1 of 11 in Best SEO and search visibility data for AI agents: https://www.anchorterminal.com/best/seo/index.md - All 46 seo comparisons: https://www.anchorterminal.com/compare/seo/index.md ## Compare - [Fetch (MCP reference server) vs Lordevo Shop](https://www.anchorterminal.com/compare/fetch-reference-server-vs-lordevo-shop.md): C 57.6 vs B 65.6 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on lordevo.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "lordevo-shop", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Lordevo Shop on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Lordevo Shop on Anchor Terminal](https://www.anchorterminal.com/badges/lordevo-shop.svg)](https://www.anchorterminal.com/tools/lordevo-shop) ``` Plain link: ```html Lordevo Shop on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Lordevo Shop is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/lordevo-shop-dark.png - Light: https://www.anchorterminal.com/assets/share/lordevo-shop-light.png - Create a video and download its frames: https://www.anchorterminal.com/assets/listing-video/index.html?listing=lordevo-shop --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp