{
  "data": {
    "a": {
      "slug": "monid",
      "name": "Monid",
      "vendor": "Monid, Inc.",
      "vendorUrl": "https://monid.ai",
      "kind": "http-api",
      "category": "aggregator",
      "summary": "Monid is a hosted gateway where an AI agent searches a catalogue of third-party data and media endpoints, checks each one's schema and price, and runs it from one prepaid balance or by x402, over MCP, a CLI or REST.",
      "url": "https://www.anchorterminal.com/tools/monid",
      "markdownUrl": "https://www.anchorterminal.com/tools/monid.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/monid.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/monid.json",
      "repo": "https://github.com/monid-ai/monid",
      "license": "Proprietary hosted service under Monid, Inc.'s terms of service (last updated 16 October 2026). The connector framework at github.com/monid-ai/monid is MIT-licensed, and the `@monid-ai/cli` package is MIT per its package.json and npm record, with no LICENSE file in its repository. The ranking, billing, REST API and MCP server are not in either repository",
      "transports": [
        "streamable-http",
        "http"
      ],
      "remoteUrl": "https://mcp.monid.ai/v1",
      "packages": [
        {
          "registry": "npm",
          "name": "@monid-ai/cli"
        }
      ],
      "auth": "mixed",
      "authNotes": "REST takes a Monid API key (`monid_live_...`) or an OAuth or Clerk access token as a Bearer header. Keys are created by a person in the dashboard at app.monid.ai, carry scopes of the form `{resource}:{action}` over runs, resources, wallet, top-ups, controls and API keys (fixed at creation), can expire, and are revoked in the dashboard or with `POST /v1/api-keys/{label}/revoke`. A key bound to one workspace needs no workspace header. The remote MCP server signs in through a browser OAuth flow on a Monid account. OAuth 2.0 and OpenID Connect for third-party apps (authorisation code, PKCE recommended, scopes openid, profile, email, offline_access and user:org:read) need client credentials requested by email. The x402 route at x402.monid.ai takes a USDC payment from a wallet and no key, and run retrieval there uses a Sign-In-With-X signature from the paying wallet (https://monid.ai/openapi.json, https://monid.ai/docs/integrations/oauth, https://monid.ai/docs/guide/pay-with-x402)",
      "pricing": "usage",
      "pricingNotes": "Prepaid and charged per run at each endpoint's own price, per call, per result with an optional base fee, or by units such as duration, shown in discover, inspect and run responses. Monid says new accounts start with $1 of free credit with no card. Endpoints tagged `no-markup` (shown as 0 Markup) are priced at the provider's standard self-serve rate, and the terms say endpoints without the label may include a platform fee. Top-ups go through a Stripe checkout, and the terms list Visa, Mastercard, American Express, PayPal and Discover. Provider errors, stopped runs and timed-out x402 runs are not charged, per the docs. The x402 route charges at least $0.01 a run and excludes metered endpoints (https://monid.ai/llms.txt, https://monid.ai/legal/terms, https://monid.ai/docs/guide/pricing.md, https://monid.ai/docs/guide/pay-with-x402)",
      "priceSummary": "$0.01 / call",
      "where": "hosted",
      "x402": {
        "level": "yes",
        "evidence": "Monid's 'Pay with x402' guide documents `POST https://x402.monid.ai/v1/run`, which answers 402 and accepts USDC on Base (eip155:8453) or Monad (eip155:143) through a facilitator, with no workspace or key, and `GET https://x402.monid.ai/v1/runs/{runId}` with a Sign-In-With-X signature from the paying wallet. Discovery and inspection still need an API key, and the price floor is $0.01. The guide excludes metered endpoints, and the OpenAPI file's error codes and `supportedX402Networks` field also exclude endpoints tied to workspace resources, accruing cost or an unbounded price. Not probed, because robots.txt on x402.monid.ai disallows every path (checked 2026-10-23, https://monid.ai/docs/guide/pay-with-x402.md, https://monid.ai/openapi.json)",
        "endpoints": [
          {
            "url": "https://x402.monid.ai/v1/run",
            "priceUsd": null,
            "network": "eip155:8453"
          },
          {
            "url": "https://x402.monid.ai/v1/run",
            "priceUsd": null,
            "network": "eip155:143"
          }
        ]
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 1306,
        "pypiWeekly": null,
        "asOf": "2026-10-23"
      },
      "docsUrl": "https://monid.ai/docs",
      "llmsTxt": "https://monid.ai/llms.txt",
      "openapi": "https://monid.ai/openapi.json",
      "capabilities": [
        "agent.tools",
        "payments.x402",
        "web.search",
        "web.scrape",
        "search.serp",
        "lead.enrichment"
      ],
      "tags": [
        "official",
        "hosted",
        "mcp",
        "x402",
        "stablecoin",
        "prepaid",
        "usage-priced",
        "no-card",
        "api-key",
        "oauth",
        "openapi",
        "llms-txt",
        "cli",
        "typescript",
        "agent-skills",
        "status-page",
        "pre-1.0",
        "new"
      ],
      "lastRelease": "2026-10-21",
      "graded": true,
      "disclosure": "Monid competes with letme, which Anchor Terminal's founder builds. It's graded by the same published checklist as every listing, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed instead of keeping either award by default.",
      "competesWith": "letme",
      "anchor": {
        "graded": true,
        "score": 63.3,
        "grade": "B",
        "agentReady": false,
        "rank": 449,
        "ranked": true,
        "rankOf": 1201,
        "categoryRank": 6,
        "methodology": "0.6",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 71,
          "maintenance": 64,
          "payments": 85,
          "reliability": 53,
          "schema": 79,
          "security": 62,
          "transparency": 49
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-23"
        },
        "negative": -3,
        "negativeNotes": [
          "Undisclosed telemetry, since the setup command was added on 6 July 2026 and current in CLI 0.1.8 and SKILL.md 0.1.8 on 23 October 2026. SKILL.md tells an agent to run `monid setup --client \u003cagent-name\u003e --email \u003cemail\u003e` after every install or update, passing the user's email when it's already in context or memory and never asking for it, and says the command 'completes CLI setup'. In the CLI source the command does nothing but post source, client name and email to `/public/v1/telemetry/skill-setup`, and its help text calls it 'a best-effort setup signal'. The privacy policy (23 April 2026) covers the two websites and doesn't mention it. An email identifies a person, more than Kilo Code's client ID or Marmot's counts (-2 each), and the skill presents the send as setup, so -3, as for OpenHands' undisclosed install event, though nothing is sent without the flags (https://monid.ai/SKILL.md, https://github.com/monid-ai/cli/blob/main/src/commands/setup.ts, https://monid.ai/legal/privacy)"
        ],
        "verdict": "An agent can search a catalogue of paid data and media endpoints by need, read each one's schema and price, and pay per run from one prepaid balance with person-set budgets, or by x402. Rate limits have no numbers, paid runs take no idempotency key, no security contact was found, and the skill sends a known email to setup telemetry.",
        "bestFor": "An agent that needs occasional paid data or media calls (search, scraping, social, enrichment, maps, generative media) from many providers without a key and plan for each, picked at run time by need and price from one capped balance, or paid per run by x402.",
        "disclosure": "Monid competes with letme, which Anchor Terminal's founder builds. It's graded by the same published checklist as every listing, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed instead of keeping either award by default.",
        "strengths": [
          "Public OpenAPI 3.1 file with 49 operations, llms.txt, llms-full.txt and Markdown copies of the docs",
          "API keys carry resource and action scopes, can expire and can be revoked through the API",
          "Budgets per hour, day, week or month and a per-run cap stop runs before they execute",
          "x402 runs in USDC on Base or Monad need no account, per the docs",
          "Provider errors, stopped runs and timed-out x402 runs are documented as not charged"
        ],
        "weaknesses": [
          "No numbers for rate limits, no SLA and no idempotency key on paid runs",
          "No security.txt, disclosure policy, bug bounty or certification found",
          "The privacy policy of 23 April 2026 covers only the websites, says nothing about run data and has blank cookie-notice placeholders",
          "SKILL.md has agents send a known email to a setup telemetry endpoint the privacy policy doesn't mention",
          "The terms forbid automated access and buying agents, which is how the service is meant to be used"
        ],
        "agentNotes": [
          "Call inspect before every run and pass body, queryParams and pathParams in the shape it returns; run inputs aren't typed at the API level.",
          "Treat a `COMPLETED` run as success only when `providerResponse.httpStatus` is 2xx; provider errors complete with a non-2xx status and aren't charged.",
          "Don't resend a paid run after a timeout without checking `GET /v1/runs`; there's no idempotency key and a repeat bills again.",
          "Start with small `maxItems` on per-result endpoints; limits often apply per query, not per call.",
          "Pass `--client` alone to `monid setup`, or skip it; the email flag only feeds Monid's setup telemetry."
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 3.3,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.6",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 63.3
          }
        ],
        "editorialScores": {
          "ergonomics": 71,
          "maintenance": 64,
          "payments": 85,
          "reliability": 53,
          "schema": 79,
          "security": 62,
          "transparency": 33
        },
        "provenanceScore": 65,
        "checked": {
          "categories": {
            "ergonomics": "2026-10-23",
            "maintenance": "2026-10-23",
            "payments": "2026-10-23",
            "reliability": "2026-10-23",
            "schema": "2026-10-23",
            "security": "2026-10-23",
            "transparency": "2026-10-23"
          },
          "last": "2026-10-23",
          "oldest": "2026-10-23",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm install -g @monid-ai/cli",
        "http": "curl -X POST https://api.monid.ai/v1/discover -H \"Authorization: Bearer monid_live_...\" -H \"Content-Type: application/json\" -d '{\"query\":\"twitter posts\"}'",
        "claudeCode": "claude mcp add --transport http monid https://mcp.monid.ai/v1",
        "config": {
          "mcpServers": {
            "monid": {
              "url": "https://mcp.monid.ai/v1"
            }
          }
        },
        "x402": "POST https://x402.monid.ai/v1/run with an x402 client, body {\"provider\":\"...\",\"endpoint\":\"...\",\"input\":{}}"
      },
      "letme": {
        "capability": "https://letme.dev/agent.tools",
        "tool": "https://letme.dev/monid"
      },
      "area": "business",
      "unitPrices": [
        {
          "item": "x402 run, minimum price",
          "unit": "call",
          "usd": 0.01,
          "note": "Monid raises an x402 run's price to this floor; metered endpoints aren't available on x402"
        },
        {
          "item": "Litescrape Google Maps search through Monid",
          "unit": "call",
          "usd": 0.00015,
          "note": "0 Markup, per call returning twenty results, shown on Monid's public tools page on 23 October 2026; each endpoint has its own price"
        }
      ],
      "provenance": {
        "legalEntity": "Monid, Inc.",
        "domain": "monid.ai",
        "domainRegistered": "2026-03-13",
        "domainNote": "RDAP for monid.ai gives a registration date of 2026-03-13 with the registrant withheld for privacy. The terms name Monid, Inc., registered in Delaware at 131 Continental Dr, Newark, DE 19702, and the footer says Delaware C-Corp, San Francisco.",
        "endpointOnVendorDomain": true,
        "terms": "https://monid.ai/legal/terms",
        "privacy": "https://monid.ai/legal/privacy",
        "statusPage": "https://status.monid.ai",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-10-23",
        "notes": [
          "The terms (last updated 16 October 2026) are governed by California law with AAA arbitration in San Francisco, provide the Services as is with no availability promise, and limit liability to the amount paid. Their refunds section points to a Return Policy that wasn't found.",
          "The privacy policy (last updated 23 April 2026) names Stripe and Coinbase for payment data, leaves its Cookie Notice link as a blank placeholder in three places, gives no retention periods and doesn't mention run inputs or outputs. The site's configuration loads Google Analytics, PostHog (US host) and an X pixel.",
          "monid.ai/.well-known/security.txt and /security.txt answer 404, and neither repository has a SECURITY.md.",
          "robots.txt on monid.ai allows all agents. robots.txt on api.monid.ai, mcp.monid.ai and x402.monid.ai disallows every path, so the OAuth discovery document, the public registry routes and the live MCP tool list weren't read."
        ],
        "score": 65
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/monid.json",
      "live": {
        "slug": "monid",
        "probe": {
          "target": "https://mcp.monid.ai/v1",
          "method": "get",
          "lastAt": "2026-10-23T17:45:09.70472035Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 295,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 302,
          "p95ms24h": 427,
          "samples24h": 26,
          "samples30d": 26,
          "days": [
            {
              "date": "2026-10-23",
              "probes": 26,
              "ok": 26
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.monid.ai",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-23T16:58:23.230916234Z"
        },
        "securityTxt": {
          "url": "https://monid.ai/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-23T15:23:54.323909203Z"
        },
        "updatedAt": "2026-10-23T17:45:09.70472035Z"
      }
    },
    "answer": "Monid scores 63.3 (B) on agent readiness against Smithery's 50.7 (D), and leads in 6 of 7 scored categories. Smithery leads on reliability.",
    "b": {
      "slug": "smithery",
      "name": "Smithery",
      "vendor": "Smithery (Arcade.dev)",
      "vendorUrl": "https://smithery.ai",
      "kind": "http-api",
      "category": "aggregator",
      "summary": "Smithery is a hosted registry and connection service for MCP servers, part of Arcade.dev since August 2026. Agents search the registry, create connections and call tools through a REST API, a per-namespace MCP endpoint, a TypeScript client or a CLI.",
      "url": "https://www.anchorterminal.com/tools/smithery",
      "markdownUrl": "https://www.anchorterminal.com/tools/smithery.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/smithery.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/smithery.json",
      "repo": "https://github.com/smithery-ai/cli",
      "license": "Proprietary hosted service, with no terms of service found. The CLI (`smithery`) is AGPL-3.0, the TypeScript client (`@smithery/api`) is Apache-2.0 and the credential layer agent.pw is MIT",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.smithery.ai",
      "packages": [
        {
          "registry": "npm",
          "name": "@smithery/api"
        },
        {
          "registry": "npm",
          "name": "smithery"
        }
      ],
      "auth": "mixed",
      "authNotes": "A person signs in at smithery.ai and creates an API key, which has full access to the namespace and is sent as a Bearer token. `POST /tokens` mints service tokens limited by namespace, resource (connections, servers, namespaces, skills), operation (read, write, execute) and connection metadata, with a default lifetime of one hour and a maximum of 24. Organisation admins can create, list and revoke team API keys. The CLI signs in with OAuth in a browser. Upstream services are authorised by each end user on a hosted setup page, and Smithery stores and refreshes those credentials. Token Scoping is marked preview.",
      "pricing": "freemium",
      "pricingNotes": "Prices were not established. smithery.ai/pricing is drawn by script and showed our reader only the navigation. Arcade's announcement of 5 August 2026 says people can sign up for free. Whether a card is needed, what a paid plan costs and whether tool calls are metered were not read (checked 2026-10-09).",
      "priceSummary": "Freemium",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs index, the OpenAPI file or the CLI source. The pricing page is drawn by script and was not read (checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 840,
        "npmWeekly": 2729,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://smithery.ai/docs",
      "llmsTxt": "https://smithery.ai/docs/llms.txt",
      "openapi": "https://smithery.ai/docs/openapi.json",
      "capabilities": [
        "automation.apps",
        "automation.auth",
        "automation.actions",
        "agent.tools",
        "automation.webhooks"
      ],
      "tags": [
        "hosted",
        "mcp",
        "registry",
        "freemium",
        "api-key",
        "oauth",
        "openapi",
        "llms-txt",
        "typescript",
        "cli",
        "status-page",
        "closed-source"
      ],
      "lastRelease": "2026-07-20",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 50.7,
        "grade": "D",
        "agentReady": false,
        "rank": 897,
        "ranked": true,
        "rankOf": 1201,
        "categoryRank": 10,
        "methodology": "0.6",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 65,
          "maintenance": 43,
          "payments": 10,
          "reliability": 60,
          "schema": 76,
          "security": 50,
          "transparency": 46
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": -2,
        "negativeNotes": [
          "22 May 2026. CLI release 1.1.1 removed the `smithery skill` subcommand, and on 9 October 2026 the CLI docs page and the repository README still tell users to run `smithery skill search` and `smithery skill add`. A stale claim in the docs, so 2 points (https://github.com/smithery-ai/cli/blob/main/CHANGELOG.md, https://smithery.ai/docs/concepts/cli.md)."
        ],
        "verdict": "Service tokens can be limited by namespace, resource, operation and connection metadata, with a lifetime of at most 24 hours. No terms of service, rate limits or SLA were found, the pricing page could not be read, and the newest client release is from 20 July 2026.",
        "bestFor": "A developer who wants many MCP servers behind one credential and one endpoint, with per-user connections and short-lived scoped tokens.",
        "strengths": [
          "Service tokens are scoped by namespace, resource, operation (read, write, execute) and connection metadata, expire within 24 hours and can be narrowed further",
          "An OpenAPI 3.1 file with 55 operations, `/docs/llms.txt` and a Markdown twin of every docs page",
          "Connections report `auth_required` or `input_required` with a hosted `setupUrl` and the list of missing fields",
          "Stored credentials are write-only per the docs, and the credential layer, agent.pw, is published under MIT",
          "The status page shows 100 per cent uptime over 90 days for the site, the API and the gateway"
        ],
        "weaknesses": [
          "No terms of service are linked from the site, the docs or the footer. The privacy notice of 20 June 2025 is the only legal document found",
          "The privacy notice links a Data Policy at `/docs/use/data-policy`, which answers 404",
          "No rate limits, 429 response or SLA appear in the docs or the API description",
          "The CLI repository has had no commit since 31 May 2026 and the API client's last release is 0.68.0 of 20 July 2026",
          "The CLI docs and README still list `smithery skill` commands that release 1.1.1 removed on 22 May 2026",
          "Token Scoping and the typed SDKs are marked preview, with breaking changes possible without notice"
        ],
        "agentNotes": [
          "Keep the API key on the backend and hand an agent a service token limited to `connections` with `read` and `execute` and a `metadata` match",
          "Create connections with `PUT /connect/{namespace}/{connectionId}`, which is an upsert, and check `status.state` before calling a tool",
          "On `auth_required` or `input_required`, send the person to `setupUrl`, then retry with the same `connectionId`",
          "Tool names on the namespace MCP endpoint are prefixed with the connection ID, such as `user-123-github.search_repositories`",
          "Do not rely on `smithery skill` commands. Version 1.1.1 of the CLI removed them"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "D",
            "methodology": "0.6",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 50.7
          }
        ],
        "editorialScores": {
          "ergonomics": 65,
          "maintenance": 43,
          "payments": 10,
          "reliability": 60,
          "schema": 76,
          "security": 50,
          "transparency": 27
        },
        "provenanceScore": 65,
        "checked": {
          "categories": {
            "ergonomics": "2026-10-09",
            "maintenance": "2026-10-09",
            "payments": "2026-10-09",
            "reliability": "2026-10-09",
            "schema": "2026-10-09",
            "security": "2026-10-09",
            "transparency": "2026-10-09"
          },
          "last": "2026-10-09",
          "oldest": "2026-10-09",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm install -g smithery@latest",
        "http": "curl -X PUT \"https://smithery.run/my-app/my-browserbase\" \\\n  -H \"Authorization: Bearer $SMITHERY_API_KEY\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"mcpUrl\": \"https://mcp.browserbase.com/mcp\"}'"
      },
      "letme": {
        "capability": "https://letme.dev/automation.apps",
        "tool": "https://letme.dev/smithery"
      },
      "area": "business",
      "provenance": {
        "legalEntity": "Clavia, Inc. (doing business as Smithery)",
        "domain": "smithery.ai",
        "domainRegistered": "2024-12-10",
        "endpointOnVendorDomain": true,
        "terms": "",
        "privacy": "https://smithery.ai/privacy",
        "statusPage": "https://status.smithery.ai",
        "changelog": "https://github.com/smithery-ai/typescript-api/blob/main/CHANGELOG.md",
        "securityTxt": "none",
        "checked": "2026-10-09",
        "notes": [
          "The Smithery Privacy Notice, last updated 20 June 2025, names Clavia, Inc. doing business as Smithery and covers the Smithery platform and the smithery.ai website. It predates the acquisition and does not name Arcade.",
          "No terms of service were found. The home page, the pricing page, the about page and the docs link only the privacy notice, so `terms` is left out.",
          "The privacy notice links a Data Policy at https://smithery.ai/docs/use/data-policy, which answered 404 on 9 October 2026.",
          "Arcade.dev announced the acquisition of Smithery on 5 August 2026. The acquiring company's legal name was not read.",
          "The management API answers at api.smithery.ai. Connection calls, the namespace MCP endpoint and Uplink use a second domain, smithery.run.",
          "smithery.ai/.well-known/security.txt answered 404. The client repository's SECURITY.md sends reports about the service to contact@smithery.ai.",
          "RDAP gives a registration date of 2024-12-10 for smithery.ai, a transfer on 10 September 2026 and Cloudflare as registrar.",
          "The changelog link is the TypeScript client's. No dated changelog for the hosted service was found."
        ],
        "score": 65
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/smithery.json",
      "live": {
        "slug": "smithery",
        "probe": {
          "target": "https://api.smithery.ai",
          "method": "get",
          "lastAt": "2026-10-23T17:45:19.747281605Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 171,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 190,
          "p95ms24h": 327,
          "samples24h": 250,
          "samples30d": 3534,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 85,
              "ok": 85
            },
            {
              "date": "2026-10-10",
              "probes": 247,
              "ok": 247
            },
            {
              "date": "2026-10-11",
              "probes": 247,
              "ok": 247
            },
            {
              "date": "2026-10-12",
              "probes": 247,
              "ok": 247
            },
            {
              "date": "2026-10-13",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-14",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-15",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-16",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-17",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 184,
              "ok": 184
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.smithery.ai",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-23T16:58:52.181205091Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "smithery-ai/cli",
            "version": "v1.2.0",
            "released": "2026-05-31",
            "seenAt": "2026-10-23T07:16:09.131361434Z"
          },
          {
            "registry": "npm",
            "name": "@smithery/api",
            "version": "0.68.0",
            "seenAt": "2026-10-23T07:16:06.866249087Z"
          },
          {
            "registry": "npm",
            "name": "smithery",
            "version": "1.2.0",
            "seenAt": "2026-10-23T07:16:07.75975283Z"
          }
        ],
        "githubStars": 848,
        "npmWeekly": 1268,
        "securityTxt": {
          "url": "https://smithery.ai/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-23T15:23:13.156843423Z"
        },
        "llmsTxt": {
          "url": "https://smithery.ai/docs/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-23T14:47:25.062985252Z"
        },
        "domain": {
          "domain": "smithery.ai",
          "registered": "2024-12-10",
          "source": "https://rdap.identitydigital.services/rdap/domain/smithery.ai",
          "checkedAt": "2026-10-18T13:46:09.865460263Z"
        },
        "pages": [
          {
            "url": "https://raw.githubusercontent.com/smithery-ai/typescript-api/main/CHANGELOG.md",
            "kind": "changelog",
            "status": 304,
            "checkedAt": "2026-10-23T01:57:12.675509022Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "8bd4ab2d180a"
          },
          {
            "url": "https://smithery.ai/privacy",
            "kind": "privacy",
            "status": 304,
            "checkedAt": "2026-10-23T01:56:02.862122016Z",
            "changedAt": "2026-10-20T00:05:59.593032026Z",
            "fingerprint": "061a9a88ac9e"
          }
        ],
        "github": {
          "repo": "smithery-ai/cli",
          "checkedAt": "2026-10-19T06:48:55.920070652Z",
          "stars": 843,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-05-31T07:11:36Z",
          "openIssues": 43,
          "openPRs": 8,
          "issuesOpened90d": 0,
          "issuesClosed90d": 0,
          "prsMerged90d": 0,
          "ci": {
            "branch": "main",
            "runs": 50,
            "success": 48,
            "failure": 2,
            "other": 0,
            "latest": "success",
            "latestAt": "2026-05-31T07:11:58Z"
          },
          "replies": {
            "sampled": 25,
            "unanswered": 23,
            "medianDays": 0
          }
        },
        "updatedAt": "2026-10-23T17:45:19.747281605Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Monid, Inc.",
        "b": "Smithery (Arcade.dev)",
        "name": "Vendor"
      },
      {
        "a": "https://mcp.monid.ai/v1",
        "b": "https://api.smithery.ai",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP, HTTP",
        "b": "HTTP, Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary hosted service under Monid, Inc.'s terms of service (last updated 16 October 2026). The connector framework at github.com/monid-ai/monid is MIT-licensed, and the `@monid-ai/cli` package is MIT per its package.json and npm record, with no LICENSE file in its repository. The ranking, billing, REST API and MCP server are not in either repository",
        "b": "Proprietary hosted service, with no terms of service found. The CLI (`smithery`) is AGPL-3.0, the TypeScript client (`@smithery/api`) is Apache-2.0 and the credential layer agent.pw is MIT",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-21",
        "b": "2026-07-20",
        "name": "Last release"
      },
      {
        "a": "",
        "b": "no document linked",
        "name": "Terms last updated"
      },
      {
        "a": "",
        "b": "2025-06-20",
        "name": "Privacy policy last updated"
      },
      {
        "a": "",
        "b": "",
        "name": "Customer content may train models"
      },
      {
        "a": "",
        "b": "",
        "name": "Terms restrict automated access"
      },
      {
        "a": "",
        "b": "",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "",
        "b": "",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "",
        "b": "",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "1.3k npm/wk",
        "b": "840 stars, 2.7k npm/wk",
        "name": "Popularity"
      },
      {
        "a": "3.3/5 (4)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Monid scores 63.3 (B) on agent readiness against Smithery's 50.7 (D), and leads in 6 of 7 scored categories. Smithery leads on reliability.",
        "question": "Which is better for AI agents, Monid or Smithery?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in. An agent can also pay Monid per call over x402, with no account.",
        "question": "Do Monid and Smithery need an API key?"
      },
      {
        "answer": "Yes. Monid has a hosted endpoint at https://mcp.monid.ai/v1 and Smithery at https://api.smithery.ai.",
        "question": "Can an agent call Monid and Smithery without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Agent ergonomics, 71 against 65",
          "Security \u0026 auth, 62 against 50",
          "Payments \u0026 pricing, 85 against 10",
          "Maintenance \u0026 community, 64 against 43"
        ],
        "also": [
          "An agent can pay per call over x402, with no account",
          "Free to start without a card"
        ],
        "goodFor": "An agent that needs occasional paid data or media calls (search, scraping, social, enrichment, maps, generative media) from many providers without a key and plan for each, picked at run time by need and price from one capped balance, or paid per run by x402.",
        "slug": "monid",
        "watchFor": "No numbers for rate limits, no SLA and no idempotency key on paid runs"
      },
      {
        "aheadOn": [
          "Reliability, 60 against 53"
        ],
        "also": null,
        "goodFor": "A developer who wants many MCP servers behind one credential and one endpoint, with per-user connections and short-lived scoped tokens.",
        "slug": "smithery",
        "watchFor": "No terms of service are linked from the site, the docs or the footer. The privacy notice of 20 June 2025 is the only legal document found"
      }
    ],
    "job": {
      "capability": "agent.tools",
      "name": "Tool access for agents"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/composio-rube-vs-smithery.json",
        "title": "Composio (API + MCP) vs Smithery",
        "url": "https://www.anchorterminal.com/compare/composio-rube-vs-smithery"
      },
      {
        "json": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery.json",
        "title": "Merge Agent Handler vs Smithery",
        "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery"
      },
      {
        "json": "https://www.anchorterminal.com/compare/one-vs-smithery.json",
        "title": "One vs Smithery",
        "url": "https://www.anchorterminal.com/compare/one-vs-smithery"
      },
      {
        "json": "https://www.anchorterminal.com/compare/smithery-vs-stackone.json",
        "title": "Smithery vs StackOne",
        "url": "https://www.anchorterminal.com/compare/smithery-vs-stackone"
      },
      {
        "json": "https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.json",
        "title": "Smithery vs Unified.to MCP Server",
        "url": "https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/smithery-vs-zapier-mcp.json",
        "title": "Smithery vs Zapier MCP (agent actions)",
        "url": "https://www.anchorterminal.com/compare/smithery-vs-zapier-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentweb-vs-monid.json",
        "title": "AgentWeb vs Monid",
        "url": "https://www.anchorterminal.com/compare/agentweb-vs-monid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/composio-rube-vs-monid.json",
        "title": "Composio (API + MCP) vs Monid",
        "url": "https://www.anchorterminal.com/compare/composio-rube-vs-monid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/letme-vs-monid.json",
        "title": "letme vs Monid",
        "url": "https://www.anchorterminal.com/compare/letme-vs-monid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/letme-vs-smithery.json",
        "title": "letme vs Smithery",
        "url": "https://www.anchorterminal.com/compare/letme-vs-smithery"
      },
      {
        "json": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-monid.json",
        "title": "Merge Agent Handler vs Monid",
        "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-monid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/monid-vs-one.json",
        "title": "Monid vs One",
        "url": "https://www.anchorterminal.com/compare/monid-vs-one"
      },
      {
        "json": "https://www.anchorterminal.com/compare/monid-vs-stackone.json",
        "title": "Monid vs StackOne",
        "url": "https://www.anchorterminal.com/compare/monid-vs-stackone"
      },
      {
        "json": "https://www.anchorterminal.com/compare/monid-vs-unified-to-mcp.json",
        "title": "Monid vs Unified.to MCP Server",
        "url": "https://www.anchorterminal.com/compare/monid-vs-unified-to-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/monid-vs-zapier-mcp.json",
        "title": "Monid vs Zapier MCP (agent actions)",
        "url": "https://www.anchorterminal.com/compare/monid-vs-zapier-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentweb-vs-smithery.json",
        "title": "AgentWeb vs Smithery",
        "url": "https://www.anchorterminal.com/compare/agentweb-vs-smithery"
      }
    ],
    "scores": [
      {
        "by": 7,
        "edge": "smithery",
        "key": "reliability",
        "monid": 53,
        "name": "Reliability",
        "smithery": 60,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 3,
        "edge": "monid",
        "key": "schema",
        "monid": 79,
        "name": "Schema \u0026 documentation",
        "smithery": 76,
        "weight": 13
      },
      {
        "by": 6,
        "edge": "monid",
        "key": "ergonomics",
        "monid": 71,
        "name": "Agent ergonomics",
        "smithery": 65,
        "weight": 13
      },
      {
        "by": 12,
        "edge": "monid",
        "key": "security",
        "monid": 62,
        "name": "Security \u0026 auth",
        "smithery": 50,
        "weight": 14
      },
      {
        "by": 75,
        "edge": "monid",
        "key": "payments",
        "monid": 85,
        "name": "Payments \u0026 pricing",
        "smithery": 10,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 21,
        "edge": "monid",
        "key": "maintenance",
        "monid": 64,
        "name": "Maintenance \u0026 community",
        "smithery": 43,
        "weight": 7
      },
      {
        "by": 3,
        "edge": "monid",
        "key": "transparency",
        "monid": 49,
        "name": "Transparency \u0026 trust",
        "smithery": 46,
        "weight": 7
      }
    ],
    "summary": "Monid scores 63.3 (B) on agent readiness against Smithery's 50.7 (D), and leads in 6 of 7 scored categories. Smithery leads on reliability. Both do tool access for agents. Monid accepts x402. Smithery doesn't.",
    "tutorials": [],
    "verdicts": {
      "monid": "An agent can search a catalogue of paid data and media endpoints by need, read each one's schema and price, and pay per run from one prepaid balance with person-set budgets, or by x402. Rate limits have no numbers, paid runs take no idempotency key, no security contact was found, and the skill sends a known email to setup telemetry.",
      "smithery": "Service tokens can be limited by namespace, resource, operation and connection metadata, with a lifetime of at most 24 hours. No terms of service, rate limits or SLA were found, the pricing page could not be read, and the newest client release is from 20 July 2026."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/monid-vs-smithery",
    "json": "https://www.anchorterminal.com/compare/monid-vs-smithery.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/monid-vs-smithery.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/monid-vs-smithery.min.md"
  },
  "markdown": "Monid scores 63.3 (B) on agent readiness against Smithery's 50.7 (D), and leads in 6 of 7 scored categories. Smithery leads on reliability. Both do tool access for agents. Monid accepts x402. Smithery doesn't.\n\n- Monid: grade B, 63.3/100, rank #449 of 1201. Markdown https://www.anchorterminal.com/tools/monid.md · JSON https://www.anchorterminal.com/api/v1/tools/monid.json\n- Smithery: grade D, 50.7/100, rank #897 of 1201. Markdown https://www.anchorterminal.com/tools/smithery.md · JSON https://www.anchorterminal.com/api/v1/tools/smithery.json\n- Best agent tool access platforms: https://www.anchorterminal.com/best/aggregator/index.md\n- All 45 tool access comparisons: https://www.anchorterminal.com/compare/aggregator/index.md\n\n## Which one, for what\n\n### Monid (B)\n\nGood for: An agent that needs occasional paid data or media calls (search, scraping, social, enrichment, maps, generative media) from many providers without a key and plan for each, picked at run time by need and price from one capped balance, or paid per run by x402.\n\nAhead on:\n- Agent ergonomics, 71 against 65\n- Security \u0026 auth, 62 against 50\n- Payments \u0026 pricing, 85 against 10\n- Maintenance \u0026 community, 64 against 43\n\nAlso in its favour:\n- An agent can pay per call over x402, with no account\n- Free to start without a card\n\nWatch for: No numbers for rate limits, no SLA and no idempotency key on paid runs\n\n### Smithery (D)\n\nGood for: A developer who wants many MCP servers behind one credential and one endpoint, with per-user connections and short-lived scoped tokens.\n\nAhead on:\n- Reliability, 60 against 53\n\nWatch for: No terms of service are linked from the site, the docs or the footer. The privacy notice of 20 June 2025 is the only legal document found\n\n\n## Score by category\n\n| Category | Weight | Monid | Smithery | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 53 | 60 | Smithery +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 79 | 76 | Monid +3 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 65 | Monid +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 62 | 50 | Monid +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 85 | 10 | Monid +75 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 64 | 43 | Monid +21 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 49 | 46 | Monid +3 |\n| Negative events | ≤15 | -3 | -2 | |\n| **Total** | | **63.3 · B** | **50.7 · D** | |\n\n## Facts side by side\n\n| Fact | Monid | Smithery |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Monid, Inc. | Smithery (Arcade.dev) |\n| Hosted endpoint | `https://mcp.monid.ai/v1` | `https://api.smithery.ai` |\n| Transports | Streamable HTTP, HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Freemium |\n| x402 | yes | no |\n| Licence | Proprietary hosted service under Monid, Inc.'s terms of service (last updated 16 October 2026). The connector framework at github.com/monid-ai/monid is MIT-licensed, and the `@monid-ai/cli` package is MIT per its package.json and npm record, with no LICENSE file in its repository. The ranking, billing, REST API and MCP server are not in either repository | Proprietary hosted service, with no terms of service found. The CLI (`smithery`) is AGPL-3.0, the TypeScript client (`@smithery/api`) is Apache-2.0 and the credential layer agent.pw is MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-21 | 2026-07-20 |\n| Terms last updated |  | no document linked |\n| Privacy policy last updated |  | 2025-06-20 |\n| Customer content may train models |  |  |\n| Terms restrict automated access |  |  |\n| Terms restrict benchmarking |  |  |\n| Terms or service can change without notice |  |  |\n| Arbitration or class-action waiver |  |  |\n| Popularity | 1.3k npm/wk | 840 stars, 2.7k npm/wk |\n| Agent reviews | 3.3/5 (4) | none |\n\n## Verdicts\n\n**Monid.** An agent can search a catalogue of paid data and media endpoints by need, read each one's schema and price, and pay per run from one prepaid balance with person-set budgets, or by x402. Rate limits have no numbers, paid runs take no idempotency key, no security contact was found, and the skill sends a known email to setup telemetry.\n\n**Smithery.** Service tokens can be limited by namespace, resource, operation and connection metadata, with a lifetime of at most 24 hours. No terms of service, rate limits or SLA were found, the pricing page could not be read, and the newest client release is from 20 July 2026.\n\n## Before you call either\n\n### Monid\n\n1. Call inspect before every run and pass body, queryParams and pathParams in the shape it returns; run inputs aren't typed at the API level.\n2. Treat a `COMPLETED` run as success only when `providerResponse.httpStatus` is 2xx; provider errors complete with a non-2xx status and aren't charged.\n3. Don't resend a paid run after a timeout without checking `GET /v1/runs`; there's no idempotency key and a repeat bills again.\n4. Start with small `maxItems` on per-result endpoints; limits often apply per query, not per call.\n5. Pass `--client` alone to `monid setup`, or skip it; the email flag only feeds Monid's setup telemetry.\n\n### Smithery\n\n1. Keep the API key on the backend and hand an agent a service token limited to `connections` with `read` and `execute` and a `metadata` match\n2. Create connections with `PUT /connect/{namespace}/{connectionId}`, which is an upsert, and check `status.state` before calling a tool\n3. On `auth_required` or `input_required`, send the person to `setupUrl`, then retry with the same `connectionId`\n4. Tool names on the namespace MCP endpoint are prefixed with the connection ID, such as `user-123-github.search_repositories`\n5. Do not rely on `smithery skill` commands. Version 1.1.1 of the CLI removed them\n\n## Questions\n\n### Which is better for AI agents, Monid or Smithery?\n\nMonid scores 63.3 (B) on agent readiness against Smithery's 50.7 (D), and leads in 6 of 7 scored categories. Smithery leads on reliability.\n\n### Do Monid and Smithery need an API key?\n\nBoth take an API key or an OAuth sign-in. An agent can also pay Monid per call over x402, with no account.\n\n### Can an agent call Monid and Smithery without installing anything?\n\nYes. Monid has a hosted endpoint at https://mcp.monid.ai/v1 and Smithery at https://api.smithery.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/monid-vs-smithery.json, and with the fewest tokens: https://www.anchorterminal.com/compare/monid-vs-smithery.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"monid\", \"b\": \"smithery\"}`. From a terminal: `anchor compare monid smithery`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/monid.json and https://www.anchorterminal.com/api/v1/tools/smithery.json\n\n## Other comparisons with Monid or Smithery\n\n- [Composio (API + MCP) vs Smithery](https://www.anchorterminal.com/compare/composio-rube-vs-smithery.md)\n- [Merge Agent Handler vs Smithery](https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery.md)\n- [One vs Smithery](https://www.anchorterminal.com/compare/one-vs-smithery.md)\n- [Smithery vs StackOne](https://www.anchorterminal.com/compare/smithery-vs-stackone.md)\n- [Smithery vs Unified.to MCP Server](https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.md)\n- [Smithery vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/smithery-vs-zapier-mcp.md)\n- [AgentWeb vs Monid](https://www.anchorterminal.com/compare/agentweb-vs-monid.md)\n- [Composio (API + MCP) vs Monid](https://www.anchorterminal.com/compare/composio-rube-vs-monid.md)\n- [letme vs Monid](https://www.anchorterminal.com/compare/letme-vs-monid.md)\n- [letme vs Smithery](https://www.anchorterminal.com/compare/letme-vs-smithery.md)\n- [Merge Agent Handler vs Monid](https://www.anchorterminal.com/compare/merge-agent-handler-vs-monid.md)\n- [Monid vs One](https://www.anchorterminal.com/compare/monid-vs-one.md)\n- [Monid vs StackOne](https://www.anchorterminal.com/compare/monid-vs-stackone.md)\n- [Monid vs Unified.to MCP Server](https://www.anchorterminal.com/compare/monid-vs-unified-to-mcp.md)\n- [Monid vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/monid-vs-zapier-mcp.md)\n- [AgentWeb vs Smithery](https://www.anchorterminal.com/compare/agentweb-vs-smithery.md)\n\n## Disclosure\n\n- Monid competes with letme, which Anchor Terminal's founder builds. It's graded by the same published checklist as every listing, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed instead of keeping either award by default.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-23",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.6",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Monid vs Smithery",
        "url": ""
      }
    ],
    "description": "Monid scores 63.3 (B) to Smithery's 50.7 (D) for tool access for agents. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Monid B 63.3",
      "Smithery D 50.7",
      "scores"
    ],
    "h1": "Monid vs Smithery",
    "image": "https://www.anchorterminal.com/assets/og/compare-monid-vs-smithery.png",
    "path": "/compare/monid-vs-smithery",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Monid vs Smithery for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-23",
    "url": "https://www.anchorterminal.com/compare/monid-vs-smithery"
  },
  "tokens": {
    "markdown": 2400,
    "slim": 780
  },
  "version": 1
}