Bring me the context.
“For Example Bookkeeping, show the latest vetted leads about Shopify payouts. Explain why they fit.”
The agent resolves the permitted brand and reads its saved leads and available source evidence.
Ask Scout for vetted social media leads, original sources and reviewed next steps from Claude or Codex. Connect over MCP, choose its access and keep the work in your conversation.
Every feature and all seven platforms. No credit card required.
Your voice. Your final say. Review, edit, and post from your own account.
Follow one fictional request for a bookkeeping business. Reading the saved lead starts no new search.
“For Example Bookkeeping, show the latest vetted leads about Shopify payouts. Explain why they fit.”
The agent resolves the permitted brand and reads its saved leads and available source evidence.
“We spend days matching Shopify payouts to orders. Can anyone recommend a bookkeeper?”
Original-post context and Scout’s assessment remain attached to the lead.
“Draft a useful reply to this lead using our bookkeeping offer.”
You check the facts, edit the draft and post from your own social account.
The next request carries a learning signal. Initial reply interest and recorded results inform related search-phrase exploration. Your authored phrases stay under your control.
See replies and learningUse these examples with your own brand and permitted records. Your key, role and current account terms determine the work available.
“Prepare a Finder search for teams asking for help with Shopify payouts.”
Scout saves the request, returns current campaign and offer choices, then prepares the exact phrase, platform and credit review. You explicitly authorize Start. Ask for that request’s status and results.
Review and Start are separate. An uncertain response is recovered using the same saved request.
See Finder“Preview the available profile lookup for this lead and show the cost.”
Scout returns source-bound targets and a current preview. After your authorization it prepares the lookup and makes its saved status and permitted evidence readable.
A lookup does not establish a verified contact or a qualified lead. Reuse the same request after an interrupted acknowledgement.
See Scout’s full job“Find Anna in this brand’s team and assign this lead to her.”
The agent discovers current permitted team choices, asks when labels are ambiguous and updates the chosen record against its current version. It reports the actual saved result.
Existing active automations can react to a sales change. Eligible undo uses the saved event and current record.
See the pipeline“Find our Sales channel connection and draft a rule for newly qualified leads.”
Scout lists permitted connection names, adapters and retained states. Your agent saves a draft and can preview an existing event. New connections and activation use the dashboard.
A connected state is the saved state, not a fresh provider health check. Editing a rule clears its prior activation approval.
See automations“Prepare one email for this lead using my permitted mailbox. Show me everything before sending.”
Scout resolves the available mailbox and exact source-backed recipient. You review the message, timing and cost ceiling. Approval and queueing are separate actions for that individual email.
No inbox reading or automatic follow-up. An uncertain send requires checking the existing send rather than sending another copy.
See the Gmail connection“Show the saved discovery activity and the API capacity this key can read.”
Read permitted run, monitoring and usage state with its dates and provenance. Ask for the same saved task when you want to check progress.
A retained status is not a new platform scan. Recurring schedules are managed in the dashboard.
See recurring discoveryYou can ask for prospecting work where you already think and plan. Your agent asks Scout for permitted leads, original source evidence and saved work, then brings that context back into the conversation.
Scout is your Agentic Coworker for social media lead discovery. Your connected agent coordinates the request. Scout supplies the prospecting context and performs the authorized work through the same account, credits and native workflows you use in the dashboard.
A request for saved leads reads saved work. It does not silently start another platform search. When you want new discovery, ask for a specific Finder search and review its scope and cost before explicitly starting it.
You choose the brands, permissions and expiry for each API key. A key remains limited by your current account and brand access. It cannot grant its own permissions or add a new brand automatically.
Ask your agent to check the same saved request. Scout returns the retained status and available result. A pending job, a completed search with no leads and unavailable source evidence are different outcomes.
If a start or generation was interrupted, recover that request before starting new paid work. Changed choices, source context or approvals can require fresh review. An uncertain email send stays a recovery task; it is not automatically sent again.
If your key expires, your membership changes or a required permission is missing, return to API & MCP in Settings. Review current access and a replacement key when needed. Connection setup and campaign schedule changes use the dashboard.
Use your agent for the request, Scout for the prospecting work and your existing tools for the handoff.
Read permitted vetted leads and available original source details. Resolve the right brand by name before choosing the records.
Request a reply, inspect a Finder search or prepare a workflow draft. New work follows current credits, permissions and approvals.
Update permitted sales records, inspect saved activity and hand a reviewed workflow back to the dashboard for activation.
Prepare the business, choose access and try a saved read. You can finish signup, verification and consent yourself.
Start free or sign in. Review your business and campaign setup, then open API & MCP in Settings.
Choose a task, brands, permissions and a lifetime from the current account policy. Review the exact key before creating it. Save the one-time secret privately.
Open API & MCPYour agent receives only the brands and permissions you review. Additions need a new key review.
Make your key available to the client as REVENUE_SCOUT_API_KEY in your private environment. Run this command, then open /mcp to check the connection.
The configuration contains placeholders, not your key. Save the key privately and supply it only to the client you chose. Configuration copied means the text was copied; check the connection in your client.
First request: “List my permitted brands in Revenue Scout, then ask which brand’s saved leads I want to read.”
“List the brands I can access in Revenue Scout, then ask which brand’s saved leads I want to read.”
Choose the correct brand. Ask for a vetted lead and its available original source. A successful read confirms that request. New paid work needs its own review.
Answers to help you decide and take the next step.
MCP is the connection your agent uses to ask Revenue Scout for authorized prospecting work. Scout itself is your Sales Prospecting Assistant for social media lead discovery. You use plain requests in the connected client; the client handles the tool calls.
Choose the instructions for your actual client: Claude Desktop, Claude Code, Codex desktop or Codex CLI. Each uses the remote Revenue Scout MCP endpoint and a scoped bearer API key. Desktop, CLI and organization settings differ, so use the matching configuration and its official client guide.
No. Ask for the brands your key can access, then choose the correct name. Scout provides authorized brand context for later requests. When names are ambiguous, your agent should ask you to choose rather than guessing.
The Settings check confirms that the key authenticates and returns permitted brand context. You still need to configure your chosen client, enable its connection and ask it to read saved work. Copying configuration confirms only that the text was copied.
Reading saved work does not start a paid job. Fresh searches, profile lookups and additional reply generation follow the same current credit terms as the dashboard. Ask for the exact review and cost before authorizing new work. Connecting an agent does not replace your balance or grant extra capacity.
With the required access, it can save the request, discover the current campaign and offer, review the phrase, platforms and publication window, then separately start the exact search you authorize. It can read that saved request’s status and results without starting a duplicate search.
You review, edit and manually post social replies from your own account. Individual Gmail email has separate permissions and exact message, recipient, mailbox, timing and cost review, followed by separate approval and queue actions. A general connection does not authorize blanket sending, inbox reading or automatic follow-up.
It can discover permitted existing destinations, save a draft, preview a selected event, read results and pause an authorized rule. You set up new connections and activate reviewed rules in the dashboard. Saving changes to a rule clears its prior activation approval.
The connection uses Scout’s existing workflows. Initial reply interest and recorded results can inform related search-phrase exploration. Repeated initial requests for the same lead do not count as new interest. This does not retrain the language model or promise a measured improvement in leads or sales.
Start free or sign in, complete your business setup, then open API & MCP in Settings. Review a scoped key, save it privately and follow the instructions for your client. Check its expiry and revocation if access is rejected. If the full key was lost, explicitly revoke it and review a replacement; it cannot be retrieved later.
Prepare your business. Choose its access. Ask for the work.