Integration

Logo.dev integration

Logo.dev returns brand data and logo files for existing companies. Look up a brand by domain, stock ticker, ISIN, crypto symbol or name (name, description, colors, social profiles, logo and brandmark with temporary download URLs), search brands by name to find their domain, fetch a logo or brandmark image record, follow brands for change events through webhook endpoints, read the account's plan and API credit balance, and flag wrong brand data for review. Lookups spend API credits (brand 5, brandmark 3, logo 2, search 1 per 1,000 searches), billed once per brand domain per route per 24 hours; a brand not found (404) or still indexing (202) is free, and an account out of credits gets HTTP 402. Webhooks need a paid plan, flagging needs Pro or above, and a commercial project on the free Community plan must show a visible 'Logos provided by Logo.dev' link. Not exposed: the image CDN (img.logo.dev, its own publishable key, meant to be loaded in browsers rather than fetched by scripts), the Transaction merchant-identification beta (its own beta key), and the routes that read or rotate a webhook signing secret. Authentication is a secret key (sk_) sent as a Bearer token in the Authorization header.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Logo.dev.Built from the 15 Logo.dev tools below, on the connection you add once.

What you can do with Logo.dev

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Webhook endpoint, 5 operations

  • create_webhook_endpointCreate webhook endpointPOSTRegisters an HTTPS URL that will receive brand.updated and brand.indexed events for real. Needs a paid plan and the owner or admin role; HTTP 409 at the plan's endpoint limit.
  • delete_webhook_endpointDelete webhook endpointDELETEDeletes a webhook endpoint for real; deliveries to it stop. Needs a paid plan and the owner or admin role. Answers 204 with no body.
  • get_webhook_endpointGet webhook endpointGETReturns one webhook endpoint (id, description, disabled, filter_types, timestamps); the delivery URL is not returned. Needs a paid plan.
  • list_webhook_endpointsList webhook endpointsGETLists the team's webhook endpoints (id, description, disabled, filter_types, timestamps); the delivery URL is not returned. Not paginated. Needs a paid plan.
  • update_webhook_endpointUpdate webhook endpointPATCHChanges a webhook endpoint for real: url, description, filter_types or disabled. Send only the fields to change; omitted fields keep their value. Needs a paid plan and the owner or admin role.

Subscription, 3 operations

  • get_brand_subscriptionGet brand subscriptionGETReturns the account's subscription to a brand's change events (subscription id, brand id, created_at), or HTTP 404 when there is none. Not billed.
  • subscribe_to_brandSubscribe to brandPUTSubscribes the account for real to brand.updated webhook events for one brand. Safe to repeat. Needs a paid plan; HTTP 409 limit_exceeded at the plan's subscription limit. Not billed.
  • unsubscribe_from_brandUnsubscribe from brandDELETEStops brand.updated webhook events for one brand (unsubscribes for real). Answers 204 whether or not a subscription existed. Needs a paid plan. Not billed.

Brand, 2 operations

  • get_brandGet brandGETReturns a brand's profile by its brand id (from look_up_brand), same shape as look_up_brand. Costs 5 API credits, billed once per brand domain per 24 hours. Use nosubscribe=true to avoid subscribing.
  • look_up_brandLook up brandGETLooks up one brand by exactly one of domain, ticker, isin, crypto or name: id, name, description, colors, socials, logo and brandmark. Costs 5 API credits. data.status not_indexed (HTTP 202) means retry in 30 s.

Account, 1 operation

  • get_accountGet accountGETReturns the account's plan (community is the free plan) and API credit balances: remaining, monthly allowance, purchased, renewal date. Not billed.

Brandmark, 1 operation

  • get_brand_brandmarkGet brand brandmarkGETReturns a brand's brandmark (the wide symbol plus wordmark lockup) as JSON (temporary download url, etag, source size, blurhash), not image bytes. Send exactly one identifier. Costs 3 API credits.

Flag, 1 operation

  • flag_domainsFlag domainsPOSTSubmits up to 100 domains whose brand data is wrong or outdated to Logo.dev reviewers. Nothing changes until a reviewer acts. Needs the Pro plan or above; 10 requests per minute. Not billed.

Logo, 1 operation

  • get_brand_logoGet brand logoGETReturns a brand's square logo as JSON (temporary download url, etag, source size and format, blurhash), not image bytes. Send exactly one identifier. Costs 2 API credits; a ready brand with no logo is still billed.

Search, 1 operation

  • search_brandsSearch brandsGETSearches brands by name and returns candidates with their name and domain; pass a domain to look_up_brand for the full profile. Costs 1 API credit per 1,000 searches, billed on every request.

Use Logo.dev from Claude Code, Cursor or Codex

Connect Logo.dev in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Logo.dev operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Logo.dev

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Logo.dev once

    Add your Logo.dev connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Logo.dev integration FAQ

What can you do with the Logo.dev integration?

LiveContext exposes 15 operations on Logo.dev, covering webhook endpoint, subscription, brand and account.

Popular integrations

Browse the whole catalog