makeBIMI

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
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-09-02'
  method: derived
created: '2026-08-21'
modified: '2026-09-03'
specificationVersion: '0.23'
tags:
- BIMI
- DMARC
- Email Authentication
- SVG
- brand indicators
- SVG 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: WellKnown
  url: well-known/makebimi-well-known.yml
- type: SecurityTxt
  url: security/makebimi-security.txt
- type: Plans
  url: plans/makebimi-plans-pricing.yml
- type: VulnerabilityDisclosure
  url: security/makebimi-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/makebimi-domain-security.yml
- 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.'
x-enrichment:
  date: '2026-09-03'
  status: minimal
  artifacts_added: 5
  pass: local-v2
x-coverage:
  state: blocked
  reason: bot-challenge
  detail: 'A Cloudflare managed challenge (HTTP 403, cf-mitigated: challenge) answers for every makebimi.com page and API
    path — including the provider''s own declared OpenAPI at /public/openapi.yaml, the APIs.json at /public/apis.json, /api-docs
    and GET /api/validate itself — leaving only the Cloudflare-exempt robots.txt, llms.txt and /.well-known/* paths readable;
    the artifacts are hidden, not absent.'
  evidence:
  - url: https://makebimi.com/public/openapi.yaml
    status: 403
  - url: https://makebimi.com/public/apis.json
    status: 403
  - url: https://makebimi.com/api-docs
    status: 403
  - url: https://makebimi.com/.well-known/security.txt
    status: 200
  - url: https://makebimi.com/llms.txt
    status: 200
  checked: '2026-09-03'