ssid.aiAPI

ssid.ai vs macvendors.com

Both turn a MAC address into a manufacturer name from the same IEEE registry. Pick macvendors.com for plain OUI-to-vendor lookup at high sustained throughput: their published plans run to 1,000,000 requests a day and they have run the service since 2011. ssid.ai charges nothing for vendor lookup at any volume. Pick ssid.ai when the vendor name is not the whole answer, because it classifies randomized (private) addresses as a typed field, carries manufacturer-cited router default logins, and ships an MCP server.

Last updated 2026-09-28 · macvendors.com figures quoted from their published plans

Side by side

ssid.aimacvendors.com
ResponseJSON: vendor, kind, randomized, confidence, sourceVendor name as a plain string
Randomized addressYes — HTTP 200, kind: randomizedHTTP 404, same as an unregistered prefix
Router default loginsYes — 550 models, manufacturer-citedNo
Compliance datasetYes — free JSON feedNo
MCP serverYes — ssid-mcp on npmNo
MAC lookup, free, no keyNo daily cap (60 / min)1,000 / day
MAC lookup, 10,000 / day$0$10 / mo
MAC lookup, 100,000 / day$0, but capped at about 86,000 / day by the 60 / min burst$40 / mo, 25 req / s
MAC lookup, 1,000,000 / dayNo tier$100 / mo
Router + compliance data1,000 / day free with a key; $15 / mo for 10,000 / day (ssid Pro)No
Vendor data sourceIEEE MA-L, re-fetched daily at 04:00IEEE, updated multiple times daily

macvendors.com prices and limits are quoted from macvendors.com/plans, checked 2026-08-08. Check it before relying on the numbers here.

Where macvendors.com is the right answer

It does one job and does it at scale. The API needs no key for the first 1,000 requests a day, returns a bare string with no parsing overhead, and the published plans sell sustained throughput ssid.ai does not: 25 requests a second on the 100,000/day plan and a 1,000,000/day plan above it. It has been running since 2011, which is a longer operating record than ssid.ai has.

If your pipeline resolves OUIs in bulk and stores a vendor name, that is the whole requirement, and routing it through a service with a lower throughput ceiling, for fields you discard, would be a bad trade.

Where ssid.ai is different

The gap shows up on addresses that are not in the vendor table. Run the same private MAC against both:

$ curl "https://ssid.ai/api/v1/lookup?mac=DA:A1:19:5F:2C:88"
{ "kind": "randomized", "randomized": true, "vendor": null,
  "confidence": 0, "explanation": "This is a randomized (private)
  address — common on modern phones …" }              # HTTP 200

$ curl "https://api.macvendors.com/DA-A1-19-5F-2C-88"
{"errors":{"detail":"Not Found"}}                      # HTTP 404

The 404 is not an error on their part; a private address genuinely has no vendor. It is undifferentiated, though: the identical response covers a rotating iPhone and a prefix the IEEE never assigned. Code that branches on the difference has to infer it. Since iOS 14 and Android 10 made per-network randomization the default, that case is common rather than exotic.

Three things follow from ssid.ai holding more than the vendor table:

  • Router default logins across 550 models — gateway IP, admin username, password and reset steps, each transcribed from the manufacturer's own documentation with the source URL attached. A field with no citation does not publish.
  • The compliance index — 67% of 550 tracked models no longer ship a universal default password, the pattern the UK PSTI Act and the EU Cyber Resilience Act target, with a free JSON feed.
  • An MCP server so an assistant calls a typed tool rather than scraping a page, plus a correction endpoint agents can write to.

How to decide

Ask what you do with a MAC address that has no vendor. If the answer is “store null and move on” at millions of rows a day, macvendors.com is sufficient and built for that volume. If the answer is “work out whether this is a phone with privacy on, then find out how to log into the router it is attached to”, that is the job ssid.ai is built for.

FAQ

Is ssid.ai or macvendors.com better for MAC address lookup?
For plain OUI-to-vendor resolution at very high sustained volume, macvendors.com: their published plans are $40/month for 100,000 requests a day at 25 requests a second, and they offer a 1,000,000/day tier ssid.ai has no equivalent for. ssid.ai does not charge for vendor lookup at any volume, but it caps bursts at 60 a minute without a key (120 on ssid Pro), which puts a practical ceiling of about 86,000 lookups a day on the free route. ssid.ai is better when the vendor name is not the whole answer — it returns a kind field that separates a randomized (private) address from a genuine registry gap, carries manufacturer-cited router default logins, and ships an MCP server.
What does ssid.ai return that macvendors.com does not?
Structured JSON instead of a vendor string: kind (universal, randomized, multicast or invalid), a randomized boolean, a confidence value, a plain-English explanation, and a source object naming the IEEE registry. On a private address such as DA:A1:19:5F:2C:88, ssid.ai answers HTTP 200 with kind: "randomized"; macvendors.com answers HTTP 404, the same response it gives for an unregistered prefix.
Is macvendors.com cheaper than ssid.ai?
For MAC/OUI lookup there is no longer a price to compare: ssid.ai does not charge for it at any volume, with or without a key. Where macvendors still wins is sustained very high throughput — ssid.ai applies a per-minute burst ceiling (60/min without a key, 120/min on ssid Pro), so roughly 86,000 lookups a day is the practical free limit and there is no lookup tier above it. If you need a million vendor lookups a day with a commitment behind it, macvendors sells that at $100/month and ssid.ai does not sell it at all. ssid.ai charges for one thing instead: ssid Pro, $15/month for 10,000 router default-login and compliance calls a day plus the submit_correction MCP tool. macvendors does not publish router data.
Do macvendors.com and ssid.ai use the same data?
For vendor resolution they use the same upstream: the IEEE registry of organizationally unique identifiers. macvendors.com states it updates from IEEE multiple times each day; ssid.ai re-fetches the MA-L registry daily at 04:00 and exposes the source URL on every response. The router default-login directory is ssid.ai's own compilation from manufacturer documentation and has no macvendors.com counterpart.
Does macvendors.com have an MCP server?
No. macvendors.com publishes an HTTP API and no MCP server, so an agent calls it as a plain web request. ssid.ai publishes ssid-mcp on npm, which exposes lookup_mac, get_router_defaults and check_router_compliance over stdio with no API key; its fourth tool, submit_correction, needs an ssid Pro key ($15/month).
Can I use both?
Yes, and for some workloads that is the sensible answer. A common split is macvendors.com for bulk vendor resolution where sustained throughput dominates, and ssid.ai where a call needs the randomized classification, a router's default credentials, or an agent-callable tool.

Related