makeBIMI

makeBIMI is a free web tool for preparing and validating brand logos for BIMI (Brand Indicators for Message Identification). It converts supported image inputs to SVG Tiny P/S, checks SVG suitability, audits a domain's DMARC configuration, and suggests a BIMI DNS TXT record. It does not issue certificates and does not guarantee mailbox-provider logo display. The public API is a single unauthenticated endpoint, GET /api/validate, for validating a remotely hosted SVG in an automated workflow. Operated alongside veriBIMI, an independent BIMI certificate-brokerage and implementation-support service, and DMARCSwiss, a Swiss-hosted DMARC monitoring service.

makeBIMI publishes 1 API on the APIs.io network: SVG Validation API. Tagged areas include BIMI, Email Authentication, DMARC, Email Deliverability, and SVG.

makeBIMI’s developer surface includes documentation, support, and 4 more developer resources.

18.7/100 emerging ▬ flat Agent 13/100 agent aware Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
1 APIs
BIMIEmail AuthenticationDMARCEmail DeliverabilitySVGBrand IndicatorsValidation

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 18.7/100 · emerging
Contract Quality 6.7 / 25
Developer Ergonomics 2.4 / 20
Access Clarity 1.1 / 20
Operational Transparency 1.4 / 13
Contract Governance 0.0 / 12
Discoverability 7.2 / 10
Agent readiness — 13/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
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 0 / 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
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
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/makebimi: 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.

makeBIMI SVG Validation API

Single unauthenticated endpoint that validates a remotely hosted SVG for BIMI suitability (SVG Tiny P/S). Described by the provider's own llms.txt as "the unauthenticated SVG va...

Resources

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: makebimi
name: makeBIMI
description: makeBIMI is a free web tool for preparing and validating brand logos for BIMI (Brand Indicators for Message Identification).
  It converts supported image inputs to SVG Tiny P/S, checks SVG suitability, audits a domain's DMARC configuration, and suggests
  a BIMI DNS TXT record. It does not issue certificates and does not guarantee mailbox-provider logo display. The public API
  is a single unauthenticated endpoint, GET /api/validate, for validating a remotely hosted SVG in an automated workflow.
  Operated alongside veriBIMI, an independent BIMI certificate-brokerage and implementation-support service, and DMARCSwiss,
  a Swiss-hosted DMARC monitoring service.
type: Index
url: https://raw.githubusercontent.com/api-evangelist/makebimi/refs/heads/main/apis.yml
created: '2026-08-21'
modified: '2026-08-21'
specificationVersion: '0.23'
tags:
- BIMI
- Email Authentication
- DMARC
- Email Deliverability
- SVG
- Brand Indicators
- Validation
tags_raw:
- BIMI
- DMARC
- email authentication
- SVG
- brand indicators
- SVG validation
apis:
- aid: makebimi:makebimi-validation-api
  name: makeBIMI SVG Validation API
  description: Single unauthenticated endpoint that validates a remotely hosted SVG for BIMI suitability (SVG Tiny P/S). Described
    by the provider's own llms.txt as "the unauthenticated SVG validation endpoint", contract GET /api/validate.
  humanURL: https://makebimi.com/api-docs
  baseURL: https://makebimi.com
  tags:
  - BIMI
  - Validation
  - Email Authentication
  properties:
  - type: Documentation
    url: https://makebimi.com/api-docs
  - type: OpenAPI
    url: https://makebimi.com/public/openapi.yaml
  - type: APIsJSON
    url: https://makebimi.com/public/apis.json
common:
- type: LLMsTxt
  url: llms/makebimi-llms.txt
- type: SecurityPolicy
  url: security/makebimi-security.txt
- type: Website
  url: https://makebimi.com
- type: Documentation
  url: https://makebimi.com/standard
- type: Support
  url: https://veribimi.com/services/
- type: PrivacyPolicy
  url: https://veribimi.com/privacy
maintainers:
- FN: Simon
  email: simon@veribimi.com
  url: https://veribimi.com
x-provenance:
  added: '2026-08-21'
  method: searched
  source: https://makebimi.com/llms.txt
  note: 'Submitted via apis.io/add on 2026-08-14 (submission 6982bc11) from simon@veribimi.com. THIS PROFILE IS DELIBERATELY
    THIN, AND NOT BECAUSE THE PROVIDER PUBLISHES LITTLE. Every substantive artifact makeBIMI publishes is unreachable to any
    non-browser client. makebimi.com sits behind a Cloudflare MANAGED CHALLENGE: /, /public/apis.json, /public/openapi.yaml,
    /api-docs, /sitemap.xml and the /api/validate endpoint itself all return HTTP 403 with `cf-mitigated: challenge` and a
    "Just a moment..." interstitial. This was tested with a default client and with a desktop Chrome user-agent; both are
    refused, so it is not user-agent filtering. Only the three paths Cloudflare exempts by default get through: robots.txt,
    llms.txt and .well-known/security.txt. Everything recorded here is drawn from those three first-party documents. The OpenAPI
    and APIs.json pointers are recorded as the provider DECLARES them in llms.txt; neither has been fetched, so neither is
    verified. The artifacts are HIDDEN, not absent. Note the contradiction, which is the provider''s to resolve: robots.txt
    says `Allow: /` for every user-agent and advertises a sitemap that is itself 403.'

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/makebimi"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/makebimi/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/makebimi/evidence"

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

Get an API key

Free tier, no email required.

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