WeSearch
FAQ · ANSWERS

Frequently asked.

Short, honest answers. Open the question to expand.

The basics
What is WeSearch?

A consumer hub on the front (a feed of news, markets, weather, and anonymous discussion) and a developer API on the back (one key, 20+ canonical resources). Think Apple News + RapidAPI, both honest.

Do I need to sign up?

No. The hub auto-creates an anonymous key on first visit. Reactions, comments, and the Pulse social tab all work immediately. You only need to provide an email if you want to keep the key across browsers.

What does "anonymous" mean here?

You're identified by a random key. Your display handle ("Plain Loom 638") is computed deterministically from that key. We never see your real name, and other users only see the handle.

What does it cost?

Nothing. WeSearch is a free community-run project — no plans, no upsells, no paywalls. There's a fair-use cap (~10k API calls/day per anonymous key) so the shared infra stays healthy. BYOK is required only for resources whose upstream provider's TOS requires it (AI completion, GIF search). If you build something heavy on top, tell us.

Using the hub
What's the Pulse tab?

The social side: trending reactions in the last 24h and recent comments across all stories. Tap a comment to jump into its thread.

How do reactions work?

Tap any of 👍 ❤️ 🔥 😂 🤔 below a card. Tap again to remove. Counts are public; who reacted is private.

Can I reply to a specific comment?

Tap the commenter's handle (or the "reply" button). The input shows "Replying to X" and your post nests under theirs. Up to 3 levels of indentation.

Can I delete my own comments?

Yes — the "delete" button only appears on your own. The body becomes "[deleted]" so reply chains stay intact. You can't delete someone else's.

How do I add my own RSS sources to the feed?

Open Discover, tap any source card to add it to "My Feeds." Switch to the "Mine" chip on the Feed tab to see only your selected sources, deduped.

Building with the API
How do I call a resource?

Three steps: POST /v1/auth/signup to mint a key, then POST /v1/r/{resource} with {"input": {...}}, with the bearer token in Authorization. The full quickstart is on the API page.

What's the firehose?

One call (GET /v1/firehose), one response containing top headlines, tech feeds, crypto prices, and earthquakes. Costs 0.2 units no matter how many providers we route to.

What's BYOK?

Bring your own key. Some resources (AI completion, schema-extract, GIF search) require you to supply your own provider credentials. We forward them per-request, never store. This avoids reselling AI tokens against the upstream TOS.

What if a provider is down?

The router fails over to the next-best alternate automatically. The composite trust score for that provider drops, future requests skip it. Visible in /v1/catalog/trust.

Privacy + safety
Where is my data?

SQLite on a single DigitalOcean droplet (NYC3). If the project grows, we'll move to replicated Postgres in the same region — still free for everyone.

What about my BYOK keys?

Stored in your browser's localStorage. Never sent to WeSearch's database — only forwarded to the upstream provider per request.

How do I report a problem?

Use the support form. We read every submission.