Dapper
Dapper was an advertising-technology and web-data company founded in 2006 by Jonathan Aizen and Eran Shir, seed-funded by Accel. It ran two surfaces: Dapper Ads, an intent-driven dynamic-ad product that pulled live product and inventory data from an advertiser's own site into targeted creative without IT integration; and open.dapper.net (the "Dapp Factory" / Dapper: The Data Mapper), a hosted tool that turned any web page into structured feeds, web services and widgets — XML, RSS, JSON, YAML, CSV, iCalendar, Google Gadgets, Netvibes modules and image loops — effectively letting anyone "create an API for any site" before providers published their own. Dapper was acquired by Yahoo! in 2010 and both surfaces were shut down; dapper.net now resolves to Yahoo nameservers with no host, and open.dapper.net no longer resolves. There is no live API, developer portal, or documentation to enrich.
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.
Dapper is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
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 — Dapper scores 6.8/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.
Resources
Every other property we hold for Dapper — 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.
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Dapper is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/dapper · machine-readable index on apis.io