MAC Address Lookup: Find Vendor, OUI & Device Type website screenshot

MAC Address Lookup: Find Vendor, OUI & Device Type

REST/JSON API, hosted MCP server, and reference data for MAC address / OUI lookup — resolving vendor, IEEE registration block, device category, and randomization confidence. Data synced twice daily from IEEE MA-L/MA-M/MA-S/IAB/CID registries. Operated by ApisOS FZE (macadress.com).

MAC Address Lookup: Find Vendor, OUI & Device Type publishes 3 API contracts indexed on the APIs.io network: Healthz API, Mac API, and Vendors API. Tagged areas include Networking, Network Access Control, Security, SecOps, and IoT.

MAC Address Lookup: Find Vendor, OUI & Device Type’s developer surface includes authentication, support, pricing, signup flow, and 25 more developer resources.

52.4/100 developing ▬ flat Agent 35/100 agent ready Front door AI 2/6 trace saas Full breakdown ↓
scored 2026-10-09 · rubric v0.23.0
AccessFreemiumSelf serve⚡ Free to try
1 published contract 1 MCP Servers
NetworkingNetwork Access ControlSecuritySecOpsIoTDevice Fleet ManagementMDMReference DataIEEE OUI LookupDeveloper ToolsMCPAgent-Native

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-09 · rubric v0.23.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/macadress: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

MAC Address Lookup: Find Vendor, OUI & Device Type Healthz API

The Healthz API from MAC Address Lookup: Find Vendor, OUI & Device Type — 1 operation(s) for healthz.

MAC Address Lookup: Find Vendor, OUI & Device Type Mac API

The Mac API from MAC Address Lookup: Find Vendor, OUI & Device Type — 2 operation(s) for mac.

MAC Address Lookup: Find Vendor, OUI & Device Type Vendors API

The Vendors API from MAC Address Lookup: Find Vendor, OUI & Device Type — 1 operation(s) for vendors.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Macadress Rate Limits

3 limits

RATE LIMITS

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Macadress Openapi Overlay

8 actions · documentation

GENERATED

Examples 5

Example request and response payloads for these APIs.

Macadress Healthz Example

4 fields

EXAMPLE

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Macadress Authentication

http/apiKey · 3 schemes

SECURITY

Macadress Domain Security

TLSv1.3 · HSTS

SECURITY

Macadress Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Macadress Agentic Access

4 operations

4 operations · 0 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 5

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
name: 'MAC Address Lookup: Find Vendor, OUI & Device Type'
aid: macadress
description: REST/JSON API, hosted MCP server, and reference data for MAC address / OUI lookup — resolving vendor, IEEE registration
  block, device category, and randomization confidence. Data synced twice daily from IEEE MA-L/MA-M/MA-S/IAB/CID registries.
  Operated by ApisOS FZE (macadress.com).
url: https://raw.githubusercontent.com/api-evangelist/mac-address-lookup-find-vendor-oui-amp-device-type/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - rate-limits
  - security
  generated: '2026-09-03'
  method: derived
created: '2026-08-28'
modified: '2026-08-28'
specificationVersion: '0.21'
tags:
- Networking
- Network Access Control
- Security
- SecOps
- IoT
- Device Fleet Management
- MDM
- Reference Data
- IEEE OUI Lookup
- Developer Tools
- MCP
- Agent-Native
tags_raw:
- Networking
- Network Access Control
- Security
- SecOps
- IoT
- Device Fleet Management
- MDM
- Reference Data
- IEEE OUI Lookup
- Developer Tools
- MCP
- Agent-Native
- agent-native
apis:
- aid: macadress:macadress-healthz-api
  name: 'MAC Address Lookup: Find Vendor, OUI & Device Type Healthz API'
  description: 'The Healthz API from MAC Address Lookup: Find Vendor, OUI & Device Type — 1 operation(s) for healthz.'
  humanURL: https://macadress.com/docs
  baseURL: https://api.macadress.com
  tags:
  - Healthz
  properties:
  - type: OpenAPI
    url: openapi/macadress-healthz-api-openapi.yml
  - type: Documentation
    url: https://macadress.com/docs
  - type: LLMsTxt
    url: https://macadress.com/llms.txt
  - type: APIReference
    url: https://macadress.com/docs
  - type: Examples
    url: examples/macadress-lookup-mac-example.json
- aid: macadress:macadress-mac-api
  name: 'MAC Address Lookup: Find Vendor, OUI & Device Type Mac API'
  description: 'The Mac API from MAC Address Lookup: Find Vendor, OUI & Device Type — 2 operation(s) for mac.'
  humanURL: https://macadress.com/docs
  baseURL: https://api.macadress.com
  tags:
  - Mac
  properties:
  - type: OpenAPI
    url: openapi/macadress-mac-api-openapi.yml
  - type: Documentation
    url: https://macadress.com/docs
  - type: LLMsTxt
    url: https://macadress.com/llms.txt
  - type: APIReference
    url: https://macadress.com/docs
  - type: Examples
    url: examples/macadress-lookup-mac-example.json
- aid: macadress:macadress-vendors-api
  name: 'MAC Address Lookup: Find Vendor, OUI & Device Type Vendors API'
  description: 'The Vendors API from MAC Address Lookup: Find Vendor, OUI & Device Type — 1 operation(s) for vendors.'
  humanURL: https://macadress.com/docs
  baseURL: https://api.macadress.com
  tags:
  - Vendors
  properties:
  - type: OpenAPI
    url: openapi/macadress-vendors-api-openapi.yml
  - type: Documentation
    url: https://macadress.com/docs
  - type: LLMsTxt
    url: https://macadress.com/llms.txt
  - type: APIReference
    url: https://macadress.com/docs
  - type: Examples
    url: examples/macadress-lookup-mac-example.json
maintainers:
- FN: ApisOS FZE
  url: https://macadress.com
  email: hello@macadress.com
generated:
  by: apis.io/add
  model: claude-opus-4-8
  confidence: 98
  at: '2026-08-28T08:50:06.984Z'
common:
- type: MCPServer
  url: https://mcp.macadress.com/mcp
- type: Overlay
  url: overlays/macadress-openapi-overlay.yaml
- type: Website
  url: https://www.macadress.com/
- type: VulnerabilityDisclosure
  url: security/macadress-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/macadress-domain-security.yml
- type: Authentication
  url: authentication/macadress-authentication.yml
- type: Packages
  url: packages/macadress-packages.yml
  description: 'Four first-party distributions: a Splunkbase add-on (TA-macadress 1.0.0, 2026-08-23), a MISP expansion module
    merged upstream 2026-08-24, an iTop/TeemIp extension whose GitHub link 404s, and a licensed .deb of the self-hosted server.
    No client SDK exists in any language and the provider says so on purpose, so no SDKs pointer is emitted.'
- type: WellKnown
  url: well-known/macadress-well-known.yml
- type: SecurityTxt
  url: well-known/macadress-security.txt
  description: RFC 9116 security.txt served at https://macadress.com/.well-known/security.txt (HTTP 200). Saved verbatim.
- type: ToolCrosswalk
  url: mcp/macadress-tool-crosswalk.yml
  description: Binds each of the four published MCP tools to its backing OpenAPI operationId. Three bind 1:1; get_vendor_block
    has no REST equivalent; healthz and the documented-but-unspecified POST /v1/mac/extract have no tool.
- type: AgentSkill
  url: skills/_index.yml
- type: Conventions
  url: conventions/macadress-conventions.yml
  description: 'Read-only surface: idempotency, dry-run and reversibility are all na rather than absent, because no operation
    mutates provider state.'
- type: Lifecycle
  url: lifecycle/macadress-lifecycle.yml
- type: Deprecation
  url: lifecycle/macadress-lifecycle.yml
  description: Additive-and-nullable compatibility policy stated in the OpenAPI info.description and enforced through a per-property
    x-added-in-version extension, plus one field (is_private) machine-marked deprecated:true with its replacement named. No
    standalone policy page, no Sunset/Deprecation headers, no removal date.
- type: ErrorCatalog
  url: errors/macadress-problem-types.yml
- type: Conformance
  url: conformance/macadress-conformance.yml
- type: DataModel
  url: data-model/macadress-data-model.yml
- type: Vocabulary
  url: vocabulary/macadress-vocabulary.yml
  description: Sixteen closed enums declared in the contract itself — IEEE block types, 802c SLAP quadrants, a 24-term device
    taxonomy, and four separate graded confidence scales.
- type: RateLimits
  url: rate-limits/macadress-rate-limits.yml
- type: Plans
  url: plans/macadress-plans-pricing.yml
- type: AgenticAccess
  url: agentic-access/macadress-agentic-access.yml
- type: Security
  url: security/macadress-vulnerability-disclosure.yml
  description: Security contact published via RFC 9116 security.txt (Contact, Expires 2027-08-22, Canonical, Preferred-Languages).
    No bug bounty, no separate disclosure policy page.
- type: DeveloperPortal
  url: https://macadress.com/mac-address-api
- type: Support
  url: https://macadress.com/contact
- type: Pricing
  url: https://macadress.com/pricing
- type: SignUp
  url: https://macadress.com/signup
- type: Login
  url: https://macadress.com/login
- type: TermsOfService
  url: https://macadress.com/terms
- type: PrivacyPolicy
  url: https://macadress.com/privacy
image: https://macadress.com/static/og-image.png
x-enrichment:
  date: '2026-08-28'
  status: enriched
  artifacts_added: 29
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/macadress"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/macadress/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/macadress/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.