Logo.dev
Company logos by domain, and brand search by name, from Logo.dev.
Connect it with: API key. Logo.dev's own documentation: https://www.logo.dev/docs/brand-search/introduction.
What agents can do
Connect Logo.dev so the agents working your tasks can reach it. With it connected, they can:
- Find a company's domain and logo by its name with Brand Search.
- Show company logos in an app by domain, using img.logo.dev image URLs with the publishable key.
- Look up brand details (name, colors, social links) for a domain.
Before you start
- A Logo.dev account (the free Community plan includes both keys).
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Logo.dev
Jaah connects to Logo.dev with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- Secret key: Sign in at logo.dev and open Dashboard > API keys (logo.dev/dashboard/api-keys); copy the Secret key, which starts with sk_.
- Publishable key (optional): On the same Dashboard > API keys page, copy the Publishable key (starts with pk_). Agents put it in img.logo.dev image URLs in the apps they build; it is safe to show in a browser.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Logo.dev card.
- Name the secret and choose who can use it.
- Fill in Secret key, Publishable key.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Logo.dev with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah calls Logo.dev's API once (GET https://api.logo.dev/v2/search?q=logo.dev&limit=1) with the stored values, and shows whether Logo.dev accepted it, or which value Logo.dev refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: secret_key, publishable_key.
Tell the agent in your task description which secret to use, for example “use the Logo.dev secret org/logo-dev”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Logo.dev once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Logo.dev's side too, revoke or delete the key at Logo.dev.
Limitations
- The free plan has a monthly request cap and requires a visible link to Logo.dev when used commercially.
- The Test runs one brand search, which counts as one request against your plan.
- Agents can do only what the connected Logo.dev account allows.
Troubleshooting
The Test says Logo.dev rejected the secret key (401)
A publishable key (pk_) was pasted as the secret key, or the key was rotated. Copy the Secret key (sk_) from Dashboard > API keys and select Replace.
Logos stop loading in a built app with 429 errors
The plan's monthly cap was reached. Check usage on the Logo.dev dashboard and upgrade, or wait for the next month.
Logos load locally but not on the live site
The publishable key has domain restrictions that do not include the site. Add the site's domain to the key on Dashboard > API keys.
Still stuck? Select Test and read the result: it names the value Logo.dev refused and the status it answered.
FAQ
Why two keys?
The secret key calls Logo.dev's API from servers and must stay private; the publishable key only loads logo images and is meant to appear in web pages.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Logo.dev account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.