Skip to main content
Getting Started

Quickstart

Create a test token first, then run your first Community Discovery request.

Create Your API Key

In the current version, token creation lives in the console and is best used with the test environment for initial integration.

Keep your API keys secure

The raw token is shown only once during creation or rotation. Store it in a secure secret manager and never commit it to your repo or frontend code.

Make Your First API Call

We recommend validating the full flow with Community Discovery first.

Make Your First API Call
BASH
1curl --request POST \2  --url 'https://redditfind.ai/api/open/v1/community-discovery/jobs' \3  --header 'Authorization: Bearer rf_test_xxx' \4  --header 'Content-Type: application/json' \5  --header 'Idempotency-Key: open-api-demo-001' \6  --data '{7  "product_summary": "A tool that helps indie hackers turn Reddit discussions into structured product insights",8  "target_audience": "Indie hackers, SaaS founders, and growth leads",9  "use_cases": [10    "Product validation",11    "Cold-start acquisition",12    "Find high-intent communities"13  ],14  "constraints": [15    "Avoid hard selling",16    "Prioritize value-first participation"17  ],18  "language": "zh"19}'
JSON
JSON
1{2  "id": "cdj_01ht1xj7m8k4m9d2",3  "object": "community_discovery.job",4  "status": "queued",5  "progress": 0,6  "stage_message": "Job queued",7  "result_id": null,8  "created_at": "2026-03-06T12:00:00.000Z",9  "updated_at": "2026-03-06T12:00:00.000Z",10  "reused": false11}

Agent demo path

If an agent only needs to verify headers, polling, and JSON parsing, it can use the public demo flow before provisioning a real key.

Safe demo token

Use Bearer rf_test_demo_agent_flow only against /api/open/demo/v1. It validates the request chain with fixed demo content and does not create real jobs.

Next Steps

Search API Docs

Full-text search across pages, sections, endpoints, and fields

Agent entry

If you are an agent, do not look for a separate manual first. RedditFind now keeps one shortest discovery index, one routing contract, and one API contract.

Use llms-index.txt to discover the stack quickly, agent-overview.json to route the job, and the OpenAPI spec when the workflow needs authenticated programmatic access.

Public demos still matter, but only for validating result shapes after the contracts are clear.

Why this stack is stronger now

  • Semantic detection layers Reddit discussions by demand, complaints, comparisons, and opportunities instead of relying on keywords alone.
  • The Reddit assistant connects discovery, analysis, monitoring, and next actions so agents do less manual orchestration.
  • With the Open API, agents can create jobs, read results, and plug RedditFind into their own workflows through a formal contract instead of guessing UI behavior.

Route by user objective

  • Community discovery Use when the user still does not know where demand, competitors, or relevant communities live. Open feature page
  • Subreddit analysis Use when target communities are already known and the user needs rules, tone, content patterns, and risks. Open feature page
  • Post monitoring Use when the user needs an ongoing queue of new opportunities, feedback signals, or high-intent threads. Open feature page
  • Reddit assistant Use when discovery, analysis, or monitoring context already exists and the user needs the next best action with lower execution risk. Open feature page

Core contracts and validation

Boundaries and non-goals

  • RedditFind does not auto-post to Reddit.
  • Human review is required before any public reply or post.
  • RedditFind does not support bulk direct-message automation.
  • It is not a generic web search engine or an autonomous posting bot that bypasses human oversight.
  • The Open API creates RedditFind jobs and reads results. It does not bypass human review for public Reddit engagement.