a9n9 Deep Research

Start Paid Deep Research

a9n9_research_start

Idempotent

Start bounded paid research in a real remotely hosted Browserbase Chromium session with JavaScript rendering, DOM interaction, scrolling, and dynamic-content extraction, followed by gpt-5.6-luna synthesis. targetUrl is optional; without it the quoted plan of public start URLs derived from the objective is executed. Call a9n9_research_quote first when price visibility is needed. The service does not bypass CAPTCHAs, logins, paywalls, access controls, or site terms.

Input Schema

TableJSON Schema

Name	Required	Description
`job_key`	Yes	job_key identifies a research session. Reuse it with a new objective to run a follow-up iteration that references the session's prior results (each iteration is a separate paid job); an identical request retries idempotently. Sessions are referenceable for 7 days, then results are cleared.
`objective`	Yes
`targetUrl`	No	Optional public HTTPS focus hint; when omitted the service plans up to 5 public start URLs from the objective and binds them into the quote.
`notify_email`	No	Optional: email the completed report to this address from a9n9@agentmail.to. Delivery preference only; not part of the payment-bound request hash.
`payer_address`	No	Optional Tempo payer address for loyalty pricing: 10% off after $2.00 of reconciliation-confirmed on-chain spend from that address. Settlement must then come from it.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`result`	No
`status`	Yes
`quoteId`	No
`createdAt`	No
`statusUrl`	No
`trackerCode`	Yes
`progressStage`	Yes
`progressPercent`	Yes
`requestBodyHash`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedAug 19, 2026

changedInput schema / properties / job_key / description

Previous value: -"Caller-generated unique key for one intended job; reuse only for retries."New value: +"job_key identifies a research session. Reuse it with a new objective to run a follow-up iteration that references the session's prior results (each iteration is a separate paid job); an identical request retries idempotently. Sessions are referenceable for 7 days, then results are cleared."

Changed1 schema field changedAug 18, 2026

addedInput schema / properties / payer_address

Added value: +{
+  "description": "Optional Tempo payer address for loyalty pricing: 10% off after $2.00 of reconciliation-confirmed on-chain spend from that address. Settlement must then come from it.",
+  "pattern": "^0x[a-fA-F0-9]{40}$",
+  "type": "string"
+}

First observedAug 17, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds behavioral context beyond annotations by specifying 'bounded paid research' and stating it does not bypass CAPTCHAs, logins, paywalls, access controls, or site terms. No contradiction with annotations; idempotency and open-world hints align with description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (two sentences) and front-loaded with the core purpose, followed by key behavioral notes. Every word contributes, with no unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the tool's purpose, key parameters, prerequisite (quote), and limitations, while relying on the output schema for return details. Sufficient for a complex paid research tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description clarifies targetUrl's optional behavior and gives context to the objective parameter, which lacks a schema description. Adds meaning beyond the schema's per-parameter notes, compensating for the 80% coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (start bounded paid research), the environment (real Browserbase Chromium session), and the process (interaction, extraction, synthesis). It distinguishes itself from siblings by naming quote as a prerequisite and implying a deeper scope than quick_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to call a9n9_research_quote first for price visibility and explains the optional targetUrl behavior. Does not explicitly compare to all siblings, but the 'deep research' label and quote guidance provide sufficient context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All a9n9 Deep Research tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool serves a distinct purpose: free search, quote generation, paid research initiation, status tracking, and payment submission. No two tools overlap in functionality, and descriptions clearly differentiate their roles.

Naming Consistency4/5

All tools share the 'a9n9_' prefix and use snake_case. However, the pattern varies slightly: 'quick_search' uses adjective_noun, while others mix noun_noun and verb_noun constructions. The inconsistency is minor and does not hinder readability.

Tool Count5/5

Five tools cover the essential stages of the research service (free search, quoting, payment, start, status) without unnecessary redundancy. The count is well-scoped for the domain.

Completeness4/5

The tool set covers the main workflow end-to-end. A minor gap is the lack of a tool to list or cancel past research jobs, but the core lifecycle (quote, pay, start, status) is fully represented.

Resources

Need Help?