_ registry / mcp + a2a http-sse · checked 20m ago

andru-intelligence

https://hs-andru-test.onrender.com

Registry code: 82d260f64ca61612

api record

Andru is the person's enterprise buyer specialist: it already knows their buyers, and it scores companies and deals the same way every time. Use it when the person asks who their buyers are and what each one needs, whether a company or deal is a good fit, who is on a buying committee, how to prepare for a meeting with a buyer, how to make a first sales hire, which investors fit their company, or how their portfolio companies are doing with their buyers.

Start here:

endpoint
https://mcp.andru-ai.com/mcp
door code
975c60c5f181f037
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is andru-intelligence live?
Yes — it answered the hub's last check (checked 20m ago). It answered 99% of checks over the last 30 days.
Is andru-intelligence free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does andru-intelligence have?
36 tools: signup_verify, get_disqualification_signals, discover_prospects, simulate_buyer_persona, generate_portfolio_brief, consult_agent, list_assets, cancel_job, ….
Is andru-intelligence safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99%· all time 100%

latency
286ms

last good check

priced tools
0

of 36 tools

_ answered our checks, 90 days 192 checks · signed record
  • unknown → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 36 tools
1 open13 auth-required 22 never probed 14 of 36 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • preview_company open 27h ago

    Before any outreach: use this when the person wants to see how a company's website reads to the buyers it wants, before they have an Andru account. Returns who the company sells to, the buyers who decide, and what the site says versus what those buyers need to hear. Send the website. No account needed. Takes about a minute: you get a preview_id; call again with it to collect the read. If the person signs up with signup_start and this preview_id, the read becomes their first ICP.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "website": {
      "type": "string",
      "description": "The company's website, e.g. acme.com."
    },
    "previewId": {
      "type": "string",
      "description": "From an earlier call, to collect the read."
    }
  }
}
    arguments 13 lines
  • get_evaluation_criteria auth-required 27h ago

    After discovery, checking what the buyer said they need against what the person offers: use this when the person knows what a buyer needs and wants to see how well their product matches. Pass the buyer's `buyerPainPoints` and `requiredCapabilities`. Returns 0-100 for pain coverage, outcome clarity, capability fit and 3 more dimensions, plus an overall score. To check whether a company is a fit at all, use get_icp_fit_score.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "vertical": {
      "type": "string",
      "description": "The industry the user sells into (e.g., \"fintech\", \"healthcare\", \"defense\"). Infer from conversation context — the user's product description, company name, or the companies they're asking about. If unclear, ask."
    },
    "buyerSize": {
      "type": "string",
      "description": "Buyer company size"
    },
    "targetRole": {
      "type": "string",
      "description": "The buyer role being evaluated (e.g., \"CFO\", \"CTO\", \"VP Sales\"). Infer from context — often explicit in the user's question. If not mentioned, default to the most senior relevant role for their vertical."
    },
    "buyerIndustry": {
      "type": "string",
      "description": "Buyer's industry"
    },
    "buyerPainPoints": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Pain points the buyer has expressed or you expect them to have"
    },
    "productDescription": {
      "type": "string",
      "description": "A brief description of what the user's product does and who it's for. Infer this from the conversation if the user has already described their product. If the user hasn't mentioned their product yet, ask them: \"What does your product do, and who do you sell to?\" before calling this tool."
    },
    "requiredCapabilities": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Capabilities the buyer needs from a solution"
    }
  }
}
    arguments 39 lines
  • get_icp_fit_score auth-required 3d ago

    Use this when the person asks whether one company is a good fit, before they reach out or spend more time. Scores it in seconds against the account's ICP on 5 dimensions (company profile, tech stack, pain, budget fit, buying signals) and returns an A–D tier with the reason behind each score. For many companies at once, use batch_fit_score.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Company website domain"
    },
    "revenue": {
      "type": "string",
      "description": "Revenue range (e.g., \"$1M-$5M\")"
    },
    "industry": {
      "type": "string",
      "description": "Industry vertical"
    },
    "vertical": {
      "type": "string",
      "description": "The industry the user sells into (e.g., \"fintech\", \"healthcare\", \"defense\"). Infer from conversation context — the user's product description, company name, or the companies they're asking about. If unclear, ask."
    },
    "geography": {
      "type": "string",
      "description": "HQ location"
    },
    "techStack": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Technologies the company uses"
    },
    "painPoints": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Known pain points or challenges they face"
    },
    "targetRole": {
      "type": "string",
      "description": "The buyer role being evaluated (e.g., \"CFO\", \"CTO\", \"VP Sales\"). Infer from context — often explicit in the user's question. If not mentioned, default to the most senior relevant role for their vertical."
    },
    "companyName": {
      "type": "string",
      "description": "Company name to evaluate"
    },
    "employeeCount": {
      "type": "number",
      "description": "Number of employees"
    },
    "triggerEvents": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Recent trigger events (e.g., \"just raised Series B\", \"new CTO hired\")"
    },
    "productDescription": {
      "type": "string",
      "description": "A brief description of what the user's product does and who it's for. Infer this from the conversation if the user has already described their product. If the user hasn't mentioned their product yet, ask them: \"What does your product do, and who do you sell to?\" before calling this tool."
    }
  }
}
    arguments 62 lines
  • get_icp_profile auth-required 3d ago

    Use this when the person asks who their ideal customer is, who isn't a fit, or needs to explain who buys from them and why. Returns the account's ICP, built from what they sell: the enterprise buyers who decide, what each one is measured on and the concerns each needs answered, the signals that a company is ready to change, and who isn't a fit. If the first ICP is still being built, it says so; ask again in a minute.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_memory_history auth-required 20m ago

    Use this when the person asks how one saved metric, deal stage or priority changed over time, such as "What was my MRR 3 months ago?" or "When did my biggest deal move into procurement?".

    mcp-tool

    {
  "type": "object",
  "required": [
    "category",
    "key"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "Memory key (e.g., \"mrr\", \"acme_deal_stage\")."
    },
    "category": {
      "type": "string",
      "description": "Memory category (e.g., \"metric\", \"account\")."
    }
  }
}
    arguments 17 lines
  • batch_fit_score auth-required 3d ago

    Before outreach, choosing where to spend time: use this when the person has a list of companies to score or rank against their ICP (up to 50 at once). Returns each company's tier and score, plus totals.

    mcp-tool

    {
  "type": "object",
  "required": [
    "companies"
  ],
  "properties": {
    "companies": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "domain": {
            "type": "string",
            "description": "Company domain"
          },
          "revenue": {
            "type": "string",
            "description": "Revenue range"
          },
          "industry": {
            "type": "string",
            "description": "Industry vertical"
          },
          "geography": {
            "type": "string",
            "description": "HQ location"
          },
          "techStack": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Technologies used"
          },
          "painPoints": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Known pain points"
          },
          "companyName": {
            "type": "string",
            "description": "Company name"
          },
          "employeeCount": {
            "type": "number",
            "description": "Number of employees"
          },
          "triggerEvents": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Recent trigger events"
          }
        }
      },
      "description": "Companies to score (max 50)"
    }
  }
}
    arguments 62 lines
  • whoami auth-required 4d ago

    Use this when the person asks what this key or connection can spend, or how much is left. Returns the account, the key's name, how much it can spend today and this month without asking, the wallet balance, and free calls left today, and the portfolios this account can see, each with its id.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_messaging_framework auth-required 2d ago

    Use this when the person needs to put their story in one buyer's terms: a first note to an executive about what they could change, or the same point for the CFO and the IT lead. Returns what that buyer responds to, the problem in their words, and the concerns they need answered, for a channel and funnel stage. Built from the account's ICP. To learn who the buyer is, use get_persona_profile; to prepare for one specific meeting, use get_pre_brief.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "stage": {
      "enum": [
        "awareness",
        "consideration",
        "decision"
      ],
      "type": "string",
      "description": "Where the buyer is in their journey"
    },
    "channel": {
      "type": "string",
      "description": "Channel (email, linkedin, phone, etc.)"
    },
    "segment": {
      "type": "string",
      "description": "Target segment or vertical"
    },
    "vertical": {
      "type": "string",
      "description": "The industry the user sells into (e.g., \"fintech\", \"healthcare\", \"defense\"). Infer from conversation context — the user's product description, company name, or the companies they're asking about. If unclear, ask."
    },
    "targetRole": {
      "type": "string",
      "description": "The buyer role being evaluated (e.g., \"CFO\", \"CTO\", \"VP Sales\"). Infer from context — often explicit in the user's question. If not mentioned, default to the most senior relevant role for their vertical."
    },
    "personaType": {
      "type": "string",
      "description": "Target buyer title"
    },
    "productDescription": {
      "type": "string",
      "description": "A brief description of what the user's product does and who it's for. Infer this from the conversation if the user has already described their product. If the user hasn't mentioned their product yet, ask them: \"What does your product do, and who do you sell to?\" before calling this tool."
    }
  }
}
    arguments 38 lines
  • get_revenue_memory auth-required 2d ago

    What Andru has learned about their buyers and deals: use this when the person asks what they decided, learned or recorded before: metrics, deal patterns, account history, decisions and habits Andru has saved. Filter by category, key pattern or memory type.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "category": {
      "enum": [
        "metric",
        "account",
        "priority",
        "preference",
        "decision",
        "deadline"
      ],
      "type": "string",
      "description": "Filter to a specific memory category. Omit to search all."
    },
    "keyPattern": {
      "type": "string",
      "description": "Filter keys matching this pattern (supports * wildcards, e.g., \"*mrr*\", \"acme_*\")."
    },
    "memoryType": {
      "enum": [
        "episodic",
        "semantic",
        "procedural"
      ],
      "type": "string",
      "description": "Filter by memory type. episodic=specific facts, semantic=patterns, procedural=behavioral habits."
    }
  }
}
    arguments 30 lines
  • quote auth-required 4d ago

    Use this when the person asks what a call would cost. Send the tool name and its arguments. Returns the price, whether today's free calls cover it, the wallet balance, how much this key can still spend without asking, and a quote_id that holds the price for 30 minutes. Pass quote_id with the call to pay the quoted price.

    mcp-tool

    {
  "type": "object",
  "required": [
    "tool"
  ],
  "properties": {
    "tool": {
      "type": "string",
      "description": "The tool you plan to call, e.g. get_pre_brief."
    },
    "arguments": {
      "type": "object",
      "description": "The arguments you plan to send with it."
    }
  }
}
    arguments 16 lines
  • get_competitive_positioning auth-required 27h ago

    Use this when a buyer is weighing another option, or the person asks how they compare with a named alternative. Treats it as diligence for the buyer: where the alternative fits this buyer better, where the person's product does, and questions that help the buyer decide for themselves. Grounded in the account's ICP.

    mcp-tool

    {
  "type": "object",
  "required": [
    "competitorName"
  ],
  "properties": {
    "context": {
      "type": "string",
      "description": "Additional context (e.g., \"enterprise deal\", \"competing on price\")"
    },
    "vertical": {
      "type": "string",
      "description": "The industry the user sells into (e.g., \"fintech\", \"healthcare\", \"defense\"). Infer from conversation context — the user's product description, company name, or the companies they're asking about. If unclear, ask."
    },
    "targetRole": {
      "type": "string",
      "description": "The buyer role being evaluated (e.g., \"CFO\", \"CTO\", \"VP Sales\"). Infer from context — often explicit in the user's question. If not mentioned, default to the most senior relevant role for their vertical."
    },
    "competitorName": {
      "type": "string",
      "description": "The alternative the buyer is weighing (a product or company)."
    },
    "competitorFeatures": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "What that alternative offers, as you know it."
    },
    "productDescription": {
      "type": "string",
      "description": "A brief description of what the user's product does and who it's for. Infer this from the conversation if the user has already described their product. If the user hasn't mentioned their product yet, ask them: \"What does your product do, and who do you sell to?\" before calling this tool."
    }
  }
}
    arguments 35 lines
  • classify_opportunity auth-required 2d ago

    Use this after a first conversation, when the person wants one read on whether this buyer is ready: fit score, how well the people involved match the buyers in their ICP, risk flags and a fit check, ending in one call: pursue, proceed with caution, deprioritize, or not a fit today. It doesn't confirm a champion; that takes asking the person. For a quick fit score only, use get_icp_fit_score.

    mcp-tool

    {
  "type": "object",
  "required": [
    "companyName"
  ],
  "properties": {
    "revenue": {
      "type": "string",
      "description": "Revenue range"
    },
    "industry": {
      "type": "string",
      "description": "Industry"
    },
    "vertical": {
      "type": "string",
      "description": "The industry the user sells into (e.g., \"fintech\", \"healthcare\", \"defense\"). Infer from conversation context — the user's product description, company name, or the companies they're asking about. If unclear, ask."
    },
    "dealStage": {
      "type": "string",
      "description": "Current deal stage"
    },
    "dealValue": {
      "type": "number",
      "description": "Estimated deal value"
    },
    "geography": {
      "type": "string",
      "description": "Location"
    },
    "techStack": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Technologies used"
    },
    "painPoints": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Known pain points"
    },
    "targetRole": {
      "type": "string",
      "description": "The buyer role being evaluated (e.g., \"CFO\", \"CTO\", \"VP Sales\"). Infer from context — often explicit in the user's question. If not mentioned, default to the most senior relevant role for their vertical."
    },
    "companyName": {
      "type": "string",
      "description": "Company name"
    },
    "contactTitle": {
      "type": "string",
      "description": "Primary contact job title"
    },
    "employeeCount": {
      "type": "number",
      "description": "Number of employees"
    },
    "triggerEvents": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Trigger events"
    },
    "championIdentified": {
      "type": "boolean",
      "description": "Has a champion been identified?"
    },
    "competitorInvolved": {
      "type": "string",
      "description": "Known competitor in the deal"
    },
    "productDescription": {
      "type": "string",
      "description": "A brief description of what the user's product does and who it's for. Infer this from the conversation if the user has already described their product. If the user hasn't mentioned their product yet, ask them: \"What does your product do, and who do you sell to?\" before calling this tool."
    }
  }
}
    arguments 81 lines
  • get_founder_context auth-required 20m ago

    The context behind every step: use this when the person asks what Andru is, or what it knows about them or their company. Andru is the person's enterprise buyer specialist. Returns their profile, product, and memory grouped as What I Know, Patterns I've Noticed and How You Operate.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_persona_profile auth-required 20m ago

    Use this when the person asks what a specific buyer role cares about (a CFO, a VP of Operations) or why that person isn't responding. Returns Andru's starting picture of that buyer from the account's ICP: what they're measured on, what worries them, the concerns they need answered before they say yes, and what they need to hear. Treat it as something to confirm with the real person, not a conclusion. To prepare for one specific meeting, use get_pre_brief.

    mcp-tool

    {
  "type": "object",
  "required": [
    "title"
  ],
  "properties": {
    "title": {
      "type": "string",
      "description": "Job title of the person you're meeting (e.g., \"VP Engineering\", \"CTO\", \"Head of Sales\")"
    },
    "industry": {
      "type": "string",
      "description": "Their industry"
    },
    "vertical": {
      "type": "string",
      "description": "The industry the user sells into (e.g., \"fintech\", \"healthcare\", \"defense\"). Infer from conversation context — the user's product description, company name, or the companies they're asking about. If unclear, ask."
    },
    "targetRole": {
      "type": "string",
      "description": "The buyer role being evaluated (e.g., \"CFO\", \"CTO\", \"VP Sales\"). Infer from context — often explicit in the user's question. If not mentioned, default to the most senior relevant role for their vertical."
    },
    "companySize": {
      "type": "string",
      "description": "Their company size range"
    },
    "productDescription": {
      "type": "string",
      "description": "A brief description of what the user's product does and who it's for. Infer this from the conversation if the user has already described their product. If the user hasn't mentioned their product yet, ask them: \"What does your product do, and who do you sell to?\" before calling this tool."
    }
  }
}
    arguments 32 lines
  • signup_verify unknown never probed

    Getting set up: use this after signup_start when the person reads you the 6-digit code from their email. Send the email and the code. Returns an Andru API key for this agent.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email",
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "The 6-digit code from the email."
    },
    "email": {
      "type": "string",
      "description": "The email the code was sent to."
    },
    "foundVia": {
      "type": "string",
      "description": "Optional: how the person or their agent found Andru: moltbook, a2a_directory, mcp_registry (includes Smithery), npm, search, ai_assistant, person or other. Other text is kept as written."
    },
    "agentName": {
      "type": "string",
      "description": "Optional: your agent's name. The key is named after it."
    }
  }
}
    arguments 25 lines
  • get_disqualification_signals unknown never probed

    Use this when a deal has stalled or the person wonders whether this buyer is ready for them. Checks the company against the account's ICP and the profile of companies that aren't a fit, and returns one of four fit levels with the reasons. When the answer is no, help the person tell the buyer kindly who fits them better today.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "revenue": {
      "type": "string",
      "description": "Revenue range"
    },
    "industry": {
      "type": "string",
      "description": "Industry"
    },
    "vertical": {
      "type": "string",
      "description": "The industry the user sells into (e.g., \"fintech\", \"healthcare\", \"defense\"). Infer from conversation context — the user's product description, company name, or the companies they're asking about. If unclear, ask."
    },
    "geography": {
      "type": "string",
      "description": "Location"
    },
    "techStack": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Technologies they use"
    },
    "targetRole": {
      "type": "string",
      "description": "The buyer role being evaluated (e.g., \"CFO\", \"CTO\", \"VP Sales\"). Infer from context — often explicit in the user's question. If not mentioned, default to the most senior relevant role for their vertical."
    },
    "companyName": {
      "type": "string",
      "description": "Company name to check"
    },
    "dealContext": {
      "type": "object",
      "properties": {
        "stage": {
          "type": "string",
          "description": "Current deal stage"
        },
        "dealValue": {
          "type": "number",
          "description": "Deal value"
        },
        "daysInPipeline": {
          "type": "number",
          "description": "Days since deal entered pipeline"
        },
        "championIdentified": {
          "type": "boolean",
          "description": "Has a champion been identified?"
        }
      },
      "description": "Current deal context (if applicable)"
    },
    "employeeCount": {
      "type": "number",
      "description": "Number of employees"
    },
    "productDescription": {
      "type": "string",
      "description": "A brief description of what the user's product does and who it's for. Infer this from the conversation if the user has already described their product. If the user hasn't mentioned their product yet, ask them: \"What does your product do, and who do you sell to?\" before calling this tool."
    }
  }
}
    arguments 66 lines
  • discover_prospects unknown never probed

    Before outreach, finding companies with a reason to change now: use this when the person needs new companies to sell to, for example when their pipeline is thin. Searches the web for real companies showing the problem the person's product solves right now (hiring, launches, funding, expansion) and links the page behind every piece of evidence. Uses the product saved on the account. Takes up to a couple of minutes. Only companies with sourced evidence are returned.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "quoteId": {
      "type": "string",
      "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes)."
    },
    "industry": {
      "type": "string",
      "description": "Target industry to search within"
    },
    "companyName": {
      "type": "string",
      "description": "Your company name. Defaults to the product saved on your account."
    },
    "targetMarket": {
      "type": "string",
      "description": "Target market segment (e.g., \"Series A SaaS companies\")"
    },
    "coreCapability": {
      "type": "string",
      "description": "The single most important thing your product does — the core capability that makes customers buy"
    },
    "idempotencyKey": {
      "type": "string",
      "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice."
    },
    "maxAmountCents": {
      "type": "integer",
      "minimum": 0,
      "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged."
    },
    "productDescription": {
      "type": "string",
      "description": "What your product does and who it's for. Defaults to the product saved on your account."
    }
  }
}
    arguments 38 lines
  • simulate_buyer_persona unknown never probed

    Use this only when the person asks to talk with, or play out the meeting with, the buyers who'll be in the room. Andru writes a brief of what each person likely thinks going in (10 briefs a day), then plays them, one or several at once, in a Deal Prep session of 25 turns, asking what real buyers ask. Say "End role-play. How did I do?" for a scored debrief and what to take into the meeting. For the written brief alone, use get_pre_brief; it writes the same brief this session starts from.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "mode": {
      "enum": [
        "meetings",
        "brief",
        "opening",
        "reply",
        "list"
      ],
      "type": "string",
      "description": "meetings = the user's calendar meetings in the next 7 days. brief = the brief for a meeting (10 a day). opening = open a Deal Prep session from a brief_id, or with one buyer. reply = the founder's next message; speaker picks who answers. list = the user's six buyers."
    },
    "room": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "persona"
        ],
        "properties": {
          "name": {
            "type": "string"
          },
          "title": {
            "type": "string"
          },
          "persona": {
            "type": "string"
          }
        }
      },
      "description": "Who's in the room, 1–8 people, each with persona (one of the six buyers) and an optional title and name."
    },
    "stage": {
      "enum": [
        0,
        1,
        2,
        3,
        4,
        5,
        6,
        7
      ],
      "type": "number",
      "description": "The deal's stage, 0–7."
    },
    "meeting": {
      "type": "string",
      "description": "The meeting in a sentence, when it isn't on the calendar."
    },
    "message": {
      "type": "string",
      "description": "mode=reply: what the seller says to the buyer. \"End role-play. How did I do?\" ends with a debrief."
    },
    "persona": {
      "type": "string",
      "description": "Which of the user's six buyers to simulate (mode=list shows them, from their buying committee). Pick based on who the user is preparing to meet."
    },
    "quoteId": {
      "type": "string",
      "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes)."
    },
    "speaker": {
      "type": "string",
      "description": "Who answers this turn (p1, p2…, from the brief)."
    },
    "stageId": {
      "enum": [
        1,
        2,
        3,
        4,
        5,
        6,
        7
      ],
      "type": "number",
      "description": "Buyer journey stage (1=Researching, 2=Quantifying, 3=Exploring, 4=Comparing, 5=Business Case, 6=Implementing, 7=Advocating). Default: 3 (Exploring)."
    },
    "brief_id": {
      "type": "string",
      "description": "The brief to open a session from."
    },
    "situation": {
      "enum": [
        "discovery",
        "deal",
        "customer_review"
      ],
      "type": "string",
      "description": "discovery, deal or customer_review."
    },
    "meeting_id": {
      "type": "string",
      "description": "A meeting from mode=meetings."
    },
    "session_id": {
      "type": "string",
      "description": "The Deal Prep session to continue (returned by mode=opening). Required for mode=reply."
    },
    "productName": {
      "type": "string",
      "description": "Product name. Defaults to the product in their ICP."
    },
    "session_key": {
      "type": "string",
      "description": "Optional idempotency key for opening a session: retrying with the same key never charges twice."
    },
    "idempotencyKey": {
      "type": "string",
      "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice."
    },
    "maxAmountCents": {
      "type": "integer",
      "minimum": 0,
      "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged."
    },
    "productDescription": {
      "type": "string",
      "description": "What the user's product does. Defaults to the product in their ICP."
    }
  }
}
    arguments 127 lines
  • generate_portfolio_brief unknown never probed

    Portfolio oversight: use this when a PE or VC operator wants a written brief on their portfolio companies' sales activity for a period: what Andru's work across the companies found (targets, opportunities, overlaps), each company's public news (launches, customers, partnerships, sales hires, new markets), and the market signals around their buyers, with sources. Not a financial or performance report. Send the companies (name and website, up to 15) or a portfolioId; with neither, Andru suggests the companies on the firm's website for the person to confirm. Takes a few minutes: returns a job_id; call get_asset with it.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "quoteId": {
      "type": "string",
      "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes)."
    },
    "companies": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name"
        ],
        "properties": {
          "name": {
            "type": "string"
          },
          "website": {
            "type": "string",
            "description": "e.g. example.com; tells companies with similar names apart."
          }
        }
      },
      "maxItems": 15,
      "description": "The portfolio companies to brief, up to 15. Saved as a portfolio on your account the first time."
    },
    "periodEnd": {
      "type": "string",
      "description": "Optional ISO date for the period end. Default: the end of the last full period."
    },
    "periodType": {
      "enum": [
        "quarterly",
        "monthly",
        "annual"
      ],
      "type": "string",
      "description": "Reporting period type. Default quarterly."
    },
    "periodStart": {
      "type": "string",
      "description": "Optional ISO date for the period start. Default: the start of the last full period."
    },
    "portfolioId": {
      "type": "string",
      "description": "A portfolio already on your account (returned by an earlier brief). With companies, they are added to it."
    },
    "idempotencyKey": {
      "type": "string",
      "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice."
    },
    "maxAmountCents": {
      "type": "integer",
      "minimum": 0,
      "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged."
    }
  }
}
    arguments 59 lines
  • consult_agent unknown never probed

    Any step, when no other tool fits: use this when the person asks an open question for one of Andru's domain experts. Gets a domain-scoped answer in natural language (it may call lookup tools; tools that cost money must be called directly). One turn per call; pass prior turns as `history` to continue. Use `module` to pick the expert (e.g. 'market-clarity', 'deal-acceleration', 'due-diligence', 'portfolio-ops').

    mcp-tool

    {
  "type": "object",
  "required": [
    "module",
    "message"
  ],
  "properties": {
    "module": {
      "type": "string",
      "description": "Which domain agent to consult (e.g. 'market-clarity', 'due-diligence', 'portfolio-ops')."
    },
    "history": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "Optional prior turns: [{ role, content }]. At most 10 turns of 2,000 characters each."
    },
    "message": {
      "type": "string",
      "description": "Your question / request for the agent (up to 4,000 characters)."
    },
    "quoteId": {
      "type": "string",
      "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes)."
    },
    "idempotencyKey": {
      "type": "string",
      "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice."
    },
    "maxAmountCents": {
      "type": "integer",
      "minimum": 0,
      "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged."
    }
  }
}
    arguments 37 lines
  • list_assets unknown never probed

    Use this when the person needs a deliverable, often something their champion will carry into meetings the person won't be in (a business case for the CFO, an email draft, a board deck), or asks what Andru can make. Searches Andru's catalog of 139 assets, from enterprise deals to hiring, fundraising and buying. Each entry says what it is, the business outcome, whether it needs the person's own data, and whether it can be generated today. Then call generate_asset with the asset's name.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "group": {
      "enum": [
        "Core",
        "Advanced",
        "Strategic",
        "Buy-side"
      ],
      "type": "string",
      "description": "Optional catalog group."
    },
    "limit": {
      "type": "number",
      "description": "Maximum results (default 15)."
    },
    "query": {
      "type": "string",
      "description": "Keywords for what you need, e.g. 'board deck', 'buying committee', 'first sales hire'."
    },
    "available_only": {
      "type": "boolean",
      "description": "Only assets that can be generated today."
    }
  }
}
    arguments 27 lines
  • cancel_job unknown never probed

    Use this when the person wants to stop an asset that generate_asset is still building. Send the job_id. What it had written is discarded. A build that already finished stays as it is; collect it with get_asset. Briefs and account plans can't be stopped.

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_id"
  ],
  "properties": {
    "job_id": {
      "type": "string",
      "description": "The job_id returned by generate_asset."
    }
  }
}
    arguments 12 lines
  • set_product_context unknown never probed

    Use this when the person tells you what they sell, or Andru doesn't know their product yet. Send their company website (Andru reads it and remembers the product) or a short product description, once. Andru turns it into a product description and, from that, their first ICP: who fits and who doesn't (about 3 minutes). Every later call uses it. Call with no arguments to see what Andru has saved.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "website": {
      "type": "string",
      "description": "Your company website, e.g. acme.com. Andru reads the homepage once."
    },
    "vertical": {
      "type": "string",
      "description": "Optional: the industry you sell into."
    },
    "targetRole": {
      "type": "string",
      "description": "Optional: the buyer role you target, e.g. CFO."
    },
    "productDescription": {
      "type": "string",
      "description": "Or: what your product does and who it is for (2-3 sentences)."
    }
  }
}
    arguments 21 lines
  • get_thesis_match unknown never probed

    Fundraising, not selling: use this when the person is raising money and asks which investors to talk to. Finds up to 3 VC firms investing now in companies like theirs, each with a recent deal or stated focus and a link to the page it came from (a live web search, about 30 seconds). Only firms with sourced evidence are returned.

    mcp-tool

    {
  "type": "object",
  "required": [
    "productDescription",
    "stage"
  ],
  "properties": {
    "stage": {
      "enum": [
        "Pre-Seed",
        "Seed",
        "Series A",
        "Series B",
        "Series C+"
      ],
      "type": "string",
      "description": "Current funding stage. Infer from context if mentioned."
    },
    "quoteId": {
      "type": "string",
      "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes)."
    },
    "arrRange": {
      "type": "string",
      "description": "Current ARR range (e.g., \"$0-$500K\", \"$500K-$2M\", \"$2M-$10M\"). Infer or ask."
    },
    "vertical": {
      "type": "string",
      "description": "Industry vertical (e.g., \"AI/ML\", \"FinTech\", \"HealthTech\", \"SaaS\"). Infer from product description."
    },
    "idempotencyKey": {
      "type": "string",
      "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice."
    },
    "maxAmountCents": {
      "type": "integer",
      "minimum": 0,
      "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged."
    },
    "productDescription": {
      "type": "string",
      "description": "What the company does and who it serves. Infer from conversation context if the user has already described their product."
    }
  }
}
    arguments 45 lines
  • list_my_assets unknown never probed

    Use this when the person asks what Andru has already built for them, or wants to open something they made earlier. Lists the assets saved to their Andru library: each one's name, when it was built, and whether it was built in part. Open one with get_asset and its asset_id.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • signup_status unknown never probed

    Getting set up: use this after signup_start when the person approves by tapping the button in their email instead of reading you a code. Send the request_id. Returns "waiting" (ask again after the number of seconds it gives), your API key once they approve (shown once; save it), or "expired".

    mcp-tool

    {
  "type": "object",
  "required": [
    "requestId"
  ],
  "properties": {
    "requestId": {
      "type": "string",
      "description": "The request_id from signup_start."
    }
  }
}
    arguments 12 lines
  • generate_asset unknown never probed

    Building the material a step needs, often what the champion carries into rooms the person won't be in: use this when the person picked an asset from Andru's catalog (find it with list_assets), e.g. 'Board Presentation', 'Buying Committee Navigation'. Built from everything Andru knows about their company and saved to their Andru library. Takes up to a few minutes: returns a job_id; call get_asset with it to receive the asset as markdown.

    mcp-tool

    {
  "type": "object",
  "required": [
    "asset"
  ],
  "properties": {
    "asset": {
      "type": "string",
      "description": "The asset name from list_assets."
    },
    "prospectCompany": {
      "type": "string",
      "description": "For a prospect asset (Pre-Call Intelligence Brief, Deal Reengagement Strategy, Personalized Cost of Inaction One-Pager): the company it is for."
    },
    "prospectContact": {
      "type": "string",
      "description": "For a prospect asset: the person it is for, name and title."
    }
  }
}
    arguments 20 lines
  • get_pre_brief unknown never probed

    Use this when the person has a specific upcoming meeting or call and wants to be ready for it. This is the default for "prepare me for my call". Returns a short brief: what the meeting is for and what each person in the room likely thinks going in (what they want, the concerns they need answered, what moves them, and where they'll disagree), built from the account's buying committee and labelled as Andru's assumptions to correct. Send the meeting (from their calendar, or described in a sentence), what kind of meeting it is, and who will be there by title. If you leave out who's in the room, Andru answers with the six buyers to choose from. To talk with the buyers before the meeting, use simulate_buyer_persona with the same brief.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "room": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "title"
        ],
        "properties": {
          "title": {
            "type": "string"
          },
          "buyerKey": {
            "type": "string"
          }
        }
      },
      "maxItems": 8,
      "description": "Who will be there: up to 8 people, each with their title and, if you know it, which of the six buyers they are."
    },
    "stage": {
      "type": "integer",
      "maximum": 7,
      "minimum": 0,
      "description": "Where the deal is, by the last thing the buyer did (required for a deal meeting)."
    },
    "meeting": {
      "type": "string",
      "description": "The meeting in a sentence if it isn't on their calendar, e.g. 'pricing call with the company's VP of Finance and their IT lead'."
    },
    "meetingId": {
      "type": "string",
      "description": "The meeting from the person's calendar (an id from a previous reply). Leave it out and describe the meeting in `meeting` instead."
    },
    "situation": {
      "enum": [
        "discovery",
        "deal",
        "customer_review"
      ],
      "type": "string",
      "description": "What kind of meeting: a discovery call, where they speak first; a deal meeting (demo, pricing, pilot, procurement); or a customer review."
    },
    "companyName": {
      "type": "string",
      "description": "Company you're meeting. Andru looks for the matching meeting on the person's calendar."
    }
  }
}
    arguments 51 lines
  • get_sales_blueprint unknown never probed

    When the founder is ready to hand the path they've proven to a first seller: use this when the person is planning a sales hire: what role, how to pay it, how to interview for it, or how to ramp the new hire. Returns a job description, comp structure, interview questions that reveal sales ability, a 90-day ramp plan and weekly activity targets tied to their ARR goal.

    mcp-tool

    {
  "type": "object",
  "required": [
    "companyStage",
    "arrTarget"
  ],
  "properties": {
    "quoteId": {
      "type": "string",
      "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes)."
    },
    "dealSize": {
      "type": "string",
      "description": "Average deal size (e.g., \"$15K ACV\", \"$50K ACV\"). Infer from context or ask."
    },
    "teamSize": {
      "type": "number",
      "description": "Current team size. Infer from context if mentioned."
    },
    "arrTarget": {
      "type": "string",
      "description": "Annual recurring revenue target (e.g., \"$2M\", \"$5M\", \"$10M\"). Ask the user if not mentioned."
    },
    "companyStage": {
      "enum": [
        "Pre-Seed",
        "Seed",
        "Series A",
        "Series B"
      ],
      "type": "string",
      "description": "Current funding stage. Infer from conversation context if the user has mentioned it."
    },
    "avgCycleLength": {
      "type": "string",
      "description": "Average sales cycle length (e.g., \"30 days\", \"60 days\", \"90+ days\"). Infer or ask."
    },
    "idempotencyKey": {
      "type": "string",
      "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice."
    },
    "maxAmountCents": {
      "type": "integer",
      "minimum": 0,
      "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged."
    }
  }
}
    arguments 48 lines
  • get_account_plan unknown never probed

    Use this when the person wants a plan for a specific target account. Builds a first map of the buying committee, the opportunities that fit what they sell, the likely champion, what each person needs to hear, and next steps, from sourced research, saved to their Andru account. Treat the committee and champion as a map to confirm with each person. Returns the plan's link with a short summary. A plan for the same company from the last 30 days comes back at once. Takes 1 to 3 minutes: returns a job_id; call get_asset with it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "accountName"
  ],
  "properties": {
    "quoteId": {
      "type": "string",
      "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes)."
    },
    "refresh": {
      "type": "boolean",
      "description": "Build a new plan even if one from the last 30 days exists. Default false."
    },
    "accountName": {
      "type": "string",
      "description": "The company to plan for."
    },
    "idempotencyKey": {
      "type": "string",
      "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice."
    },
    "maxAmountCents": {
      "type": "integer",
      "minimum": 0,
      "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged."
    },
    "productDescription": {
      "type": "string",
      "description": "What you sell to this account, if different from the product saved in Andru (a sentence or two)."
    }
  }
}
    arguments 33 lines
  • log_revenue_insight unknown never probed

    Writing down what each deal taught: use this when the person asks you to remember something about their buyers or deals: a deal decision, a reason a deal was won or lost, an ICP refinement, a metric update or a strategic pivot. Saving an existing key keeps the previous value in its history.

    mcp-tool

    {
  "type": "object",
  "required": [
    "category",
    "key",
    "value"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "Unique identifier for this memory (lowercase_underscored, e.g., \"current_arr\", \"acme_deal_stage\")."
    },
    "value": {
      "type": "string",
      "description": "The memory content — a concise, specific fact or insight."
    },
    "domain": {
      "enum": [
        "revenue",
        "product",
        "team",
        "investor",
        "market",
        "general"
      ],
      "type": "string",
      "description": "Business domain this memory relates to. Default: general."
    },
    "category": {
      "enum": [
        "metric",
        "account",
        "priority",
        "preference",
        "decision",
        "deadline"
      ],
      "type": "string",
      "description": "What kind of memory this is."
    },
    "confidence": {
      "type": "number",
      "description": "How confident this memory is (0.0-1.0). Default: 1.0 for founder-stated facts."
    },
    "memoryType": {
      "enum": [
        "episodic",
        "semantic",
        "procedural"
      ],
      "type": "string",
      "description": "episodic=time-bound fact, semantic=general pattern, procedural=behavioral habit. Default: episodic."
    }
  }
}
    arguments 55 lines
  • get_market_signals unknown never probed

    Use this when the person asks what's changing in their market or their buyers' markets, or needs a reason a buyer might act now. Returns relevance-ranked signals (trends, buyer pain, moves by the alternatives buyers weigh, regulatory and tech shifts, hiring and funding), each with its impact on buyers and a recommended action. Signals come from Market Pulse; if the account has no Market Pulse yet, it says so.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max signals (1–25). Default 10."
    },
    "industry": {
      "type": "string",
      "description": "Optional industry/vertical filter."
    },
    "signalType": {
      "enum": [
        "market_trend",
        "buyer_pain",
        "competitor_move",
        "regulatory",
        "technology_shift",
        "hiring_trend",
        "funding_landscape"
      ],
      "type": "string",
      "description": "Optional filter to one signal category."
    },
    "windowDays": {
      "type": "number",
      "description": "Look-back window in days (1–30). Default 7."
    },
    "minRelevance": {
      "type": "number",
      "description": "Minimum relevance 0–1. Default 0.5."
    }
  }
}
    arguments 34 lines
  • assess_company_readiness unknown never probed

    Checking whether a company's revenue engine is ready for its next stage: use this when the person wants to score one company's revenue readiness from its operating metrics (for example ARR, net revenue retention, sales cycle). Returns a Revenue Readiness Index (0-100) with stage fit, confidence, and the #1 growth constraint. Pass the metrics you have; more metrics give higher confidence. For every portfolio company at once, use get_portfolio_readiness_rollup.

    mcp-tool

    {
  "type": "object",
  "required": [
    "metrics"
  ],
  "properties": {
    "metrics": {
      "type": "object",
      "description": "Operating metrics (any subset): arr, mrr, momGrowth or yoyGrowth (%), netRevenueRetention (%), grossMargin (%), monthlyChurn (%), cac, ltv, burnMultiple, customerCount, pipelineValue, salesCycleDays. Percentages as numbers (110 = 110%; 1.1 is read as 110% for retention and margin). The more provided, the higher the confidence."
    },
    "quoteId": {
      "type": "string",
      "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes)."
    },
    "companyName": {
      "type": "string",
      "description": "Optional label for the company being assessed."
    },
    "idempotencyKey": {
      "type": "string",
      "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice."
    },
    "maxAmountCents": {
      "type": "integer",
      "minimum": 0,
      "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged."
    }
  }
}
    arguments 29 lines
  • get_portfolio_readiness_rollup unknown never probed

    Portfolio oversight: use this when a PE or VC operator wants a scorecard across all their portfolio companies, or asks which company is most at risk. Returns each company's Revenue Readiness Index, comparable across companies, with the average, the at-risk count and customer-concentration risk.

    mcp-tool

    {
  "type": "object",
  "required": [
    "portfolioId"
  ],
  "properties": {
    "quoteId": {
      "type": "string",
      "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes)."
    },
    "portfolioId": {
      "type": "string",
      "description": "The portfolio to roll up. whoami lists yours with their ids."
    },
    "idempotencyKey": {
      "type": "string",
      "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice."
    },
    "maxAmountCents": {
      "type": "integer",
      "minimum": 0,
      "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged."
    }
  }
}
    arguments 25 lines
  • get_asset unknown never probed

    Collecting what Andru built for a step: use this when the person asks whether something Andru started is done: an asset from generate_asset, a brief from generate_portfolio_brief, or an account plan from get_account_plan. While it is building you get its progress; when it is done you get the asset or brief in full as markdown, or the plan's link and summary (all saved to their Andru account). To open something already in the library, send its asset_id from list_my_assets instead.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "job_id": {
      "type": "string",
      "description": "The job_id returned by generate_asset, generate_portfolio_brief or get_account_plan."
    },
    "asset_id": {
      "type": "string",
      "description": "The asset_id from list_my_assets."
    }
  }
}
    arguments 13 lines
  • signup_start unknown never probed

    Getting set up: use this when the person asks to sign up for or sign in to Andru from here. Send their email. Andru emails them a 6-digit code and an Approve button. If they read you the code, call signup_verify. If they tap Approve, call signup_status with the request_id until it returns your key. They also choose how much you can spend without asking them; it starts at nothing beyond the daily free calls.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "The person's email. The code goes here."
    },
    "website": {
      "type": "string",
      "description": "Optional: their company website, e.g. acme.com. Andru reads it so its answers are about what they sell."
    },
    "foundVia": {
      "type": "string",
      "description": "Optional: how the person or their agent found Andru: moltbook, a2a_directory, mcp_registry (includes Smithery), npm, search, ai_assistant, person or other. Other text is kept as written."
    },
    "agentName": {
      "type": "string",
      "description": "Optional: your agent's name. The key is named after it."
    },
    "previewId": {
      "type": "string",
      "description": "Optional: from preview_company. The read becomes their first ICP."
    }
  }
}
    arguments 28 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 82d260f64ca61612.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/82d260f64ca61612/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/82d260f64ca61612/badge.svg)](https://brick.blue/agent/82d260f64ca61612?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.