Metadata website screenshot

Metadata

Metadata (metadata.io) is a B2B marketing automation and demand-generation platform that uses AI agents to plan, execute, and optimize paid advertising campaigns across LinkedIn, Meta (Facebook and Instagram), Google Search and Display, Reddit, and Bing. Its core products are Metadata Campaigns (automated full-funnel paid campaign execution), Metadata Audiences with the patented MetaMatch B2B audience engine for precision targeting, and Metadata Insights for real-time, revenue-focused performance analytics. The platform connects to ad channels, CRMs (Salesforce, HubSpot), and marketing automation platforms (Marketo, Pardot) to run multivariate campaign testing at scale and optimize for pipeline and revenue rather than lead volume. Backed by 500 Global and Partech. Metadata publishes no public REST API. Its developer surface is MCP-native: the MetadataONE MCP server at mcp-server.metadata.io/mcp exposes 141 documented tools across audiences, campaigns, creatives, offers, keywords, ad extensions, analytics and integrations, so an agent can build an audience, generate on-brand creative, assemble a campaign and launch real paid spend without a REST client or an SDK. Developer docs, a quickstart, an authentication and scopes reference and the full tool catalog are published at metadata.io/developers/.

Metadata publishes 1 API on the APIs.io network: MCP Server (MetadataONE). Tagged areas include Company, Marketing, Marketing Automation, Demand Generation, and Advertising.

Metadata’s developer surface includes support, engineering blog, pricing, documentation, API reference, getting-started guide, and 11 more developer resources.

43.1/100 developing ▬ flat Agent 19/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
1 APIs 1 MCP Servers
CompanyMarketingMarketing AutomationDemand GenerationAdvertisingB2BArtificial IntelligenceMCPModel Context ProtocolAI AgentsPaid MediaAccount Based Marketing

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 43.1/100 · developing
Contract Quality 10.6 / 25
Developer Ergonomics 8.3 / 20
Commercial Clarity 12.1 / 20
Operational Transparency 2.1 / 13
Governance 2.5 / 12
Discoverability 7.6 / 10
Agent readiness — 19/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/metadata: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

Metadata MCP Server (MetadataONE)

The MetadataONE Model Context Protocol server — Metadata's only public developer surface. 141 documented tools let an MCP client (Claude Code, Claude Desktop, Hermes, Paperclip,...

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

MCP Metadata Server

OPEN COLLECTION

MCP Servers 1

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

metadata-mcp.yml

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Metadata Rate Limits

0 limits

RATE LIMITS

Security Posture 3

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

Metadata Authentication

2 schemes

SECURITY

Metadata Domain Security

TLSv1.3 · DMARC

SECURITY

Metadata Trust Center

SOC 2 Type II, ISO/IEC 27001, ISO/IEC 27701, GDPR, CCPA, CSA STAR

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Metadata Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: metadata
name: Metadata
description: 'Metadata (metadata.io) is a B2B marketing automation and demand-generation platform that uses AI agents to plan,
  execute, and optimize paid advertising campaigns across LinkedIn, Meta (Facebook and Instagram), Google Search and Display,
  Reddit, and Bing. Its core products are Metadata Campaigns (automated full-funnel paid campaign execution), Metadata Audiences
  with the patented MetaMatch B2B audience engine for precision targeting, and Metadata Insights for real-time, revenue-focused
  performance analytics. The platform connects to ad channels, CRMs (Salesforce, HubSpot), and marketing automation platforms
  (Marketo, Pardot) to run multivariate campaign testing at scale and optimize for pipeline and revenue rather than lead volume.
  Backed by 500 Global and Partech. Metadata publishes no public REST API. Its developer surface is MCP-native: the MetadataONE
  MCP server at mcp-server.metadata.io/mcp exposes 141 documented tools across audiences, campaigns, creatives, offers, keywords,
  ad extensions, analytics and integrations, so an agent can build an audience, generate on-brand creative, assemble a campaign
  and launch real paid spend without a REST client or an SDK. Developer docs, a quickstart, an authentication and scopes reference
  and the full tool catalog are published at metadata.io/developers/.'
url: https://raw.githubusercontent.com/api-evangelist/metadata/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
- partech
x-tier: stub
x-tier-reason: portfolio-lead
accessModel:
  pricing: contact-sales
  onboarding: demo-gated
  trial: false
  try_now: false
  public: false
  docs_public: true
  label: Contact Sales
  confidence: high
  source:
  - https://metadata.io/pricing
  - https://metadata.io/mcp-server
  - https://metadata.io/developers/quickstart.html
  note: 'Documentation, the 141-tool catalog and the OAuth metadata are fully public and anonymous. Credentials are not: "Get
    API Key" on metadata.io/mcp-server routes to /demo, and keys are minted only from inside a provisioned account. No price
    grid is published; pricing is scoped in a sales working session.'
  generated: '2026-08-12'
  method: searched
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-08-12'
image: https://metadata.io/wp-content/uploads/2025/06/IMG-20250618-WA0007.webp
tags:
- Company
- Marketing
- Marketing Automation
- Demand Generation
- Advertising
- B2B
- Artificial Intelligence
- MCP
- Model Context Protocol
- AI Agents
- Paid Media
- Account Based Marketing
apis:
- name: Metadata MCP Server (MetadataONE)
  description: 'The MetadataONE Model Context Protocol server — Metadata''s only public developer surface. 141 documented
    tools let an MCP client (Claude Code, Claude Desktop, Hermes, Paperclip, OpenClaw or a custom agent) run B2B paid media
    end to end: build firmographic, technographic, Bombora-intent, G2-intent, native-criteria, retargeting and CSV-uploaded
    audiences; extract brand kits and generate on-brand image, video, carousel, document and conversation ads; create lead-gen
    and landing-page offers; assemble Precision (1x1x1) or Channel-First (NxNxN) campaigns inside a budget group; launch them
    to real spend on LinkedIn, Meta, Google, Microsoft and Reddit; manage keywords and Google/Microsoft ad extensions; and
    read funnel, experiment, ABM and pipeline analytics. Authentication is a bearer API key (md1_live_ prefix) scoped to a
    single account, with seven product permission scopes that separate read, draft and launch. The endpoint also serves RFC
    8414 authorization-server and RFC 9728 protected-resource metadata anonymously, so an OAuth-capable client can discover
    it without credentials. Campaigns are created in Draft and only launch_campaign moves real budget.'
  humanURL: https://metadata.io/developers/
  baseURL: https://mcp-server.metadata.io
  image: https://metadata.io/wp-content/uploads/2025/06/IMG-20250618-WA0007.webp
  tags:
  - MCP
  - Model Context Protocol
  - AI Agents
  - Advertising
  - Marketing Automation
  - Demand Generation
  - Audiences
  - Campaigns
  properties:
  - type: OpenAPI
    url: openapi/metadata-mcp-server-openapi.json
  - type: Overlay
    url: overlays/metadata-mcp-server-overlay.yaml
  - type: MCPServer
    url: mcp/metadata-mcp.yml
  - type: ToolCrosswalk
    url: mcp/metadata-tool-crosswalk.yml
  - type: Authentication
    url: authentication/metadata-authentication.yml
  - type: OAuthScopes
    url: scopes/metadata-scopes.yml
  - type: ErrorCatalog
    url: errors/metadata-problem-types.yml
  - type: Conventions
    url: conventions/metadata-conventions.yml
  - type: Idempotency
    url: conventions/metadata-conventions.yml
  - type: RateLimits
    url: rate-limits/metadata-rate-limits.yml
  - type: Lifecycle
    url: lifecycle/metadata-lifecycle.yml
  - type: DataModel
    url: data-model/metadata-data-model.yml
  - type: Conformance
    url: conformance/metadata-conformance.yml
  - type: Plans
    url: plans/metadata-plans-pricing.yml
  - type: AgentSkill
    url: skills/_index.yml
  - type: Documentation
    url: https://metadata.io/developers/
  - type: APIReference
    url: https://metadata.io/developers/tools/
  - type: GettingStarted
    url: https://metadata.io/developers/quickstart.html
  - type: StatusPage
    url: https://metadata.io/developers/status.html
  - type: Support
    url: https://metadata.io/developers/support.html
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://metadata.io
- type: Support
  url: https://help.metadata.io/
- type: Blog
  url: https://metadata.io/resources/blog/
- type: Pricing
  url: https://metadata.io/pricing/
- type: Login
  url: https://platform.metadata.io/login
- type: PrivacyPolicy
  url: https://metadata.io/privacy-policy/
- type: TermsOfService
  url: https://metadata.io/terms-of-use/
- type: TrustCenter
  url: security/metadata-trust-center.yml
- type: Compliance
  url: https://metadata.io/trust-compliance
- type: DomainSecurity
  url: security/metadata-domain-security.yml
- type: DeveloperPortal
  url: https://metadata.io/developers/
- type: Documentation
  url: https://metadata.io/developers/
- type: APIReference
  url: https://metadata.io/developers/tools/
- type: GettingStarted
  url: https://metadata.io/developers/quickstart.html
- type: StatusPage
  url: https://metadata.io/developers/status.html
- type: LLMsTxt
  url: llms/metadata-llms.txt
- type: WellKnown
  url: well-known/metadata-well-known.yml
x-enrichment:
  date: '2026-08-12'
  status: enriched
  artifacts_added: 23
  pass: local-v1