Add Neurobird Search to the services registry

[seblosiv]

Motivation

Neurobird Search is a web search API built for agents rather than for people clicking links. One call fans out across several search engines, fuses the rankings with reciprocal rank fusion, fetches and extracts the top pages, and ranks the passages inside them, so a result arrives with the part of the page that answers the query already extracted and a follow up fetch is usually unnecessary. When a grounded answer is requested, every supporting quote is matched back against its source text and a quote that fails the match is returned marked unverified rather than silently dropped.

• Service name: Neurobird Search
• Live service URL: https://search.neurobird.com
• Provider URL: https://neurobird.com
• OpenAPI or API reference URL: https://search.neurobird.com/openapi.json

Summary

• The service is live and accepts MPP payments.
• This PR adds or updates its entry in schemas/services.ts.
• Listed endpoints, prices, and payment methods match the live service.
• Public documentation and icon URLs are stable and accessible.
• pnpm generate:discovery succeeds.
• pnpm check:types passes.
• pnpm build succeeds.

Update: I have now run the toolchain rather than leaving those three boxes on trust. On Node 23.9 / pnpm 10.22 (the repo asks for Node >= 24, so pnpm warns about the engine, and all three still complete):

$ pnpm generate:discovery
Generated public/services/llms.txt (143 services)
Generated schemas/discovery.json (143 services, 1457 endpoints)
Generated public/services/catalog.json (143 services)
Generated schemas/discovery.example.json (3 services)
  1078 paid, 196 dynamic, 183 free
exit 0

$ pnpm check:types      # tsc --noEmit
exit 0

$ pnpm build
vite build: built in 47.76s
[ssg] 395 files generated
exit 0

The generated schemas/discovery.json contains the entry as expected: Neurobird Search, https://search.neurobird.com, one paid endpoint POST /paid/search, intent charge, method evm, USDC on Base.

The only red check on this PR is Vercel, which is the fork deploy authorization your bot flagged and needs a Tempo team member. Socket Security, label, contributor guidance and changed-services all pass.

Verification of the service itself, using your own CLI:

$ npx mppx validate https://search.neurobird.com
Discovery (/openapi.json)
  ✓ Document found and parseable
  ✓ Valid OpenAPI structure
  ✓ Paid endpoints found (2 endpoint(s))
POST /paid/search
  ✓ Returns 402 without credentials
  ✓ WWW-Authenticate header present (Payment scheme)
  ✓ Challenge parseable (evm/charge)
  ✓ Challenge has id / realm / expires in the future
  ✓ Realm matches server hostname
  ✓ Valid recipient address
  ✓ Valid currency address (mainnet)
  ✓ Amount is valid integer string
  ✓ Has chainId (8453)
  Error Handling
  ✓ Malformed credential returns 402 (not 500)
  ✓ Error response includes fresh challenge

Summary: 31 passed, 2 skipped

Key design considerations

• Integration: third-party
• Payment methods and intents: evm charge, USDC on Base (chainId 8453), settled through the x402 exact flow via https://x402.org/facilitator, which is the arrangement evm.charge({ ..., x402: { facilitator } }) describes in the docs. This PR adds an EVM_BASE_USDC_PAYMENT constant alongside the existing Tempo and Stripe ones, since every current entry is Tempo or Stripe. Very happy to drop it and use a different pattern if you would rather shape EVM entries another way.
• Provider relationship: I own and operate the service.
• Directory fit: No existing entry is a duplicate. The nearest listings are SerpApi and Brave Search, which return links and snippets, and Exa. What is different here is that the passage extraction and the answer grounding happen inside the same call, and that quote verification is exposed to the caller as a per quote verified boolean rather than being an internal detail. Priced at $0.005 per request.
• Disclosure: the service is live and in production, but it is newly launched, so it has no usage history yet. Entirely reasonable if you would rather wait for that before adding it to a curated list.

Also registered on MPPScan: https://mppscan.com/server/4bf664e29dcf63d2b6f633ccb74ff9151ee4fea0e6c8465544ada55f5cc958fd

[vercel]

Someone is attempting to deploy a commit to the Tempo Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thanks for submitting a service to the MPP directory!

Complete the service pull request template in your PR description before review. It contains the current submission requirements and review criteria.

Service submission guide

[github-actions]

🔀 Changed Services

✅ Added

• neurobird-search

[seblosiv]

Quick status from my side, in case it helps triage.

The service PR template in the description is complete: motivation, all seven summary
checkboxes, and the key design considerations section. I also ran your toolchain locally
rather than ticking those boxes on trust (generate:discovery, check:types, build all
exit 0 on Node 23.9 / pnpm 10.22), and the generated discovery.json contains the entry as
POST /paid/search, intent charge, method evm, USDC on Base.

The only red check is the Vercel preview deploy, which needs a Tempo team member to authorize
a deploy from a fork. That one is not actionable from my side, so I have left it alone.

Service is still live and unchanged at https://search.neurobird.com. Happy to reshape the
EVM_BASE_USDC_PAYMENT constant if you would rather EVM entries followed a different pattern
from the Tempo and Stripe ones, just say which shape you want.

[github-actions]

Closing this PR. The recommended way to list your service is through MPPScan—it follows the standard MPP discovery format and makes your service immediately discoverable by agents, no PR required.

[github-actions]

Closing this PR. The recommended way to list your service is through MPPScan—it follows the standard MPP discovery format and makes your service immediately discoverable by agents, no PR required.