RB2B
RB2B is a US-focused B2B website visitor identification platform that resolves anonymous web traffic into person-level leads — names, LinkedIn profiles, hashed and plaintext business emails, mobile ad IDs, and full business profiles — and pushes them to sales, marketing, and ad-tech systems. The product is delivered as a JavaScript pixel plus a knowledge- base and pipeline of 50+ destination integrations (Slack, Microsoft Teams, Salesforce, HubSpot, Clay, Zapier, Apollo, Customer.io, Demandbase, and others), with global company-level identification and US-only person- level resolution. RB2B operates a separate API Partner Program at api.rb2b.com that exposes credit-metered Identification endpoints (IP → HEM, IP → MAID, IP → Company Domain) and Enrichment endpoints (HEM → LinkedIn, HEM → Business Profile, HEM → MAID, LinkedIn → Email, LinkedIn → Phone, Email → LinkedIn, Email → MAID) for SaaS developers, GTM engineers, retailers, and ad-tech platforms that want to embed identity resolution into their own apps and identity graphs. The platform is SOC 2 Type II certified.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles RB2B the way a machine reads it — 5 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — RB2B scores 14.6/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile RB2B
Each block below is one kind of artifact we hold for RB2B. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
RB2B Identification API
Credit-metered Identification endpoints that convert anonymous web signals (IP addresses and user agents) into business identifiers, including IP → HEM (hashed email), IP → MAID...
RB2B Enrichment API
Credit-metered Enrichment endpoints that take a known identifier (hashed email, LinkedIn URL, plaintext email, MAID, or company domain) and return additional B2B attributes — Li...
RB2B Pixel and Destination Webhooks
The RB2B JavaScript pixel installed in a site header (or via Google Tag Manager / Segment / RudderStack / Shopify / Webflow / WordPress / HubSpot CMS / Wix) is the primary data ...
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for RB2B — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/rb2b · machine-readable index on apis.io