DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to monitor live brand citations with your DataForSEO account with Cited

Connect your own DataForSEO credentials so Cited scans supported AI surfaces for real answers.

Credentials. DataForSEO credentials are stored in .cited/config.env, so keep that file private and never paste the keys into shared logs or prompts.

Who it is forAn SEO or marketing operator who already has a DataForSEO account and needs live evidence of how AI assistants cite the brand.

The problemMock data cannot show what AI assistants actually say about the brand, and the operator must supply their own provider credentials.

The outcomeCited running in live mode through the DataForSEO adapter, with scan runs recording citations and mentions for configured prompts.

What you need first

  • Docker Compose v2
  • Node.js 22 or newer
  • About 4 GB RAM recommended
  • A domain and brand you want to monitor
  • DataForSEO API credentials, only if you want live monitoring instead of mock mode

Steps

  1. Obtain DataForSEO API credentials
  2. Configure the provider and credentials in .cited/config.env following docs/providers/dataforseo.md
  3. Run npm run self-host:down && npm run self-host:up
  4. Run npm run self-host:doctor to check the installation
  5. Verify your domain, configure your brand, and add monitored prompts and surfaces in the web app

Prompt for your agent

In the cited-cc/cited repo, configure DataForSEO credentials in .cited/config.env using docs/providers/dataforseo.md, restart with the self-host commands, and run self-host:doctor. Report which surfaces are available for the configured provider and whether the doctor check passed. Verify that no credential values are printed in the output.

Caveat. Surface availability depends on the selected provider, and DataForSEO requires operator-supplied credentials, so not every surface will return results.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page