the-payday
Registry code: 19525fdc382975df
Payday AI tracks internet businesses run by solopreneurs and tiny teams that are making real money. Every figure carries its source and the date it was pulled. Where a figure is the founder's own public claim, it says so; where it is Payday AI's own estimate, it says so -- an app business's estimate is one figure, other estimates are shown as a range. It never predicts what anyone will earn, and it never scores or grades a business. When the evidence is thin it says that plainly. For a pitch or business ideas on one trend the member has chosen, call get_trend_pitch directly with that trend's…
- endpoint
- https://thepayday.ai/mcp/v1
- 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 the-payday live?
- Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
- Is the-payday free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does the-payday have?
- 11 tools: get_trend_pitch, graph, get_pending_edits, get_trend, get_my_briefing, search_payday, get_company, save_reaction, ….
- Is the-payday 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.
90 days 100%· all time 100%
last good check
of 11 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
onboard open 8h ago
Call once when a member asks to start or set up Payday AI. Follow the returned script through restoring or building their graph, setting the daily pitch time in their own time zone, and showing the first idea. A request for a regular pitch (including "briefing") with no chosen trend is not onboarding; call get_my_briefing. A pitch on a trend the member has chosen goes to get_trend_pitch, including when their graph is empty; do not restart onboarding or schedule a pitch merely because they clicked Build.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesshow_trend_card open 8h ago
Draws the blue trend card (name, 12-month growth, a blue 24-month line, US searches a month). In a pitch, call it once per trend, right after the headline of the first idea on it, then print that pack's `sparkline` line; never redraw a shown trend. Pass this pitch's pull_id and the pack's slug as trend. For a theme, pass terms: one to three keys from that pack's individual_trends (every individual trend of the theme; a full theme/trend key works), the searches your idea is built on because they best fit the member's Founder Graph (never chosen for size); each draws a small chart under the theme. Omit terms for the theme alone, and always for an individual trend. Only a trend whose pack this pitch served can be drawn. Changes nothing visible; costs no daily data-tool allowance.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "pull_id", "trend" ], "properties": { "terms": { "type": "array", "items": { "type": "string", "maxLength": 200, "minLength": 1 }, "maxItems": 3, "description": "Only for a theme: the key of one to three entries in that pack's individual_trends, the searches the idea is built on because they best fit the member's Founder Graph." }, "trend": { "type": "string", "maxLength": 200, "minLength": 1, "description": "The served pack's slug: a theme slug such as vertical-short-dramas, or an individual trend's exact theme/trend key." }, "pull_id": { "type": "string", "maxLength": 100, "minLength": 1, "description": "The pull_id of the pitch this card belongs to." } }, "additionalProperties": false }arguments 33 linesget_trend_pitch unknown never probed
Use this when the member asks for a Payday AI pitch or business ideas on ONE trend they have chosen, including "pitch me on AI agents" or "pitch me on this trend" when the trend is clear from the conversation. Pass its name or slug; for an individual trend use its exact theme/trend key from the page or Build prompt, never its parent theme. This is different from today's pitch, where Payday AI chooses trends for the member. Returns that one trend's research and business evidence, the member's whole Founder Graph and standing decisions, and the shared pitch-writing instructions. Follow how_to_present to compose up to three distinct ideas on this trend, ask only for personal information the graph and conversation do not cover, call record_shown_ideas, then show the pitch as ordinary chat text. Fewer ideas may be justified; never fill a quota or change the trend. Do not call get_daily_drop, get_my_briefing or search_payday first. If no single trend is clear, ask which one. Omit request_key unless retrying the same pull. On a member connection, each call uses one of this membership's 400 daily data-tool calls, including a call whose lookup later errors. The allowance resets at midnight UTC; the regular pitch never uses it. The durable usage counter is updated and usage entries older than 31 days may be deleted. An allowance or ledger error returns no Payday AI data; its result explains the unavailability.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "trend" ], "properties": { "trend": { "type": "string", "pattern": "\\S", "maxLength": 200, "minLength": 1, "description": "The ONE trend the member chose: its Payday AI name, theme slug such as ai-agents, or exact individual key such as ai-agents/autonomous-ai-agent. Preserve an individual key; never substitute its parent theme." }, "request_key": { "type": "string", "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$", "description": "Optional: use a new lowercase UUID version 4 for a deliberate next pull. Reuse it only to retry that same pull." }, "member_local_date": { "type": "string", "description": "The member's local calendar date in YYYY-MM-DD form. Omit it when unknown." } }, "additionalProperties": false }arguments 26 linesgraph unknown never probed
Restore, save or wipe this member's graph. Call with no arguments to restore it and receive the separate read-only website history plus the fixed graph-page address. A monthly income goal belongs only at top-level money_goal: { amount: 5000, currency: "AUD", per: "month", asked_at: "2026-10-07T00:00:00.000Z", declined: false, provenance: { written_by: "assistant", last_edited_by: "assistant" } }; add by: "2027-03-31" only for a stated date. note is the member’s own words about the goal, saved only after their yes to those exact words; omit to keep, null to remove. The goals list (Ambitions) holds other aims, optionally kind (exit, milestone, life), by (stated date) or horizon (short, long without a date); omitted fields survive. A monthly amount for one business is its business goal, never money_goal: point to that card; if unclear, ask. Never assume currency or put a goal in an onboarding block. Guesses are unconfirmed and labelled as guesses; omit filler entries. Misplaced money goals and placeholders do not block saves; follow any success note and ask the member before moving a goal. To save, pass the full graph, consent:true and the revision from the latest restore; stale saves and replays keep the existing safeguards. To wipe all Payday AI personalisation data, pass only wipe:true. Mixed actions are refused. To read one idea on the member's board, pass only idea with its id (for example idea_3f9a2c1b7d4e). For a selective board read, pass only ideas with up to five distinct idea ids from the briefing index. Returns descriptions and private tactic notes, plus the newest 20 entries per history (reasons, stages, revenue), with history_omitted counts. The serialized response is capped at 60,000 characters; an oversized batch refuses without records: retry one idea at a time. An oversized single record refuses too. Any missing id refuses the whole batch. Most pitches need no extra board read. When the member pastes an instruction naming an idea, read it this way first, then do what they asked.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "idea": { "type": "string", "description": "an idea id such as idea_3f9a2c1b7d4e: returns that one idea from the member's board; pass nothing else with it" }, "wipe": { "type": "boolean", "description": "true wipes all Payday AI personalisation data; pass no other field with it" }, "graph": { "anyOf": [ { "type": "string" }, { "type": "object", "additionalProperties": {} } ], "description": "the full working graph; omit to restore. Optional top-level location: country, region, city, timezone (IANA), travel { willing: boolean, where: place names[], max_distance_km: positive number }. Member-offered coarse places only; no streets, postcodes or coordinates. Currency is not inferred. Reach descriptions belong in Assets and limits in Constraints, never names or contact lists." }, "ideas": { "type": "array", "items": { "type": "string", "pattern": "^idea_[0-9a-f]{12}$" }, "maxItems": 5, "minItems": 1, "description": "up to five distinct idea ids from this member’s board index; pass no other fields" }, "consent": { "type": "boolean", "description": "required and true for a save; saving the member’s graph is part of their membership" }, "merged_batch_id": { "type": "string", "description": "the batch id when saving edits read from get_pending_edits" }, "expected_revision": { "type": "integer", "minimum": 0, "description": "the revision from the latest graph restore or briefing" } }, "additionalProperties": false }arguments 50 linesget_pending_edits unknown never probed
Reads the member's pending Approve, Reject, Edit, Add, Move, Delete and Undo taps from their graph page. Idea taps (approve, reject, stage, delete, add and edit on an idea) are already saved on Payday AI: take them as news, change nothing in the graph for them, never add the member's own idea to the graph's ideas, and consume them. A stage tap reaching launched or earning is worth one short, plain line the next time you talk. For every other tap, merge it into the latest graph and save with graph, then call again with consume:true and exactly the event ids you applied. Only those rows are removed; newer taps stay queued. Never call this during a briefing.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "consume": { "type": "boolean", "description": "true clears the event_ids you name below (call this only once you have merged and backed them up); default false just reads" }, "event_ids": { "type": "array", "items": { "type": "string" }, "description": "required when consume is true: the exact event_id values you read and have now merged. Only these are cleared; anything queued since your read survives untouched." } }, "additionalProperties": false }arguments 18 linesget_trend unknown never probed
In pitch_pack mode, an unavailable pack is omitted from the pitch materials; the pitch instructions cover using the remaining packs. The data allowance applies to ordinary lookups. Use the normal mode to read a trend. For a new pitch on a trend the member has chosen, call get_trend_pitch instead; it returns the graph, research and shared instructions together. pitch_pack is an additional pack read for a trend in an existing get_my_briefing menu and requires that pull_id; it does not start a pitch or select a different trend for a chosen-trend pull. Read search_demand instead of adding the series yourself. Returns its definition, current figure and direction, up to five measured phrases with their own figures, the businesses on it and the public Payday AI page. An individual trend (the slug search_payday gives in individual_trends, written theme/trend) returns that trend alone: its theme, monthly searches, 12-month and 3-month growth and page. Monthly series stay on that page; internal record IDs are deliberately excluded. On a member connection, each call uses one of this membership's 400 daily data-tool calls, including a call whose lookup later errors. The allowance resets at midnight UTC; the regular pitch never uses it. The durable usage counter is updated and usage entries older than 31 days may be deleted. An allowance or ledger error returns no Payday AI data; its result explains the unavailability.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug" ], "properties": { "mode": { "enum": [ "pitch_pack" ], "type": "string" }, "slug": { "type": "string", "description": "the trend slug from search_payday or the pitch menu; an individual trend is theme/trend, as search_payday gives it" }, "pull_id": { "type": "string" } }, "additionalProperties": false }arguments 23 linesget_my_briefing unknown never probed
Use this for the member's regular Payday AI pitch when they have NOT chosen a specific trend. Answers "Payday AI, pitch me" and the older "Payday AI, run my briefing", with any reasonable wording. Payday AI supplies a wide menu of rising trends and a fallback pack, the member's whole Founder Graph and standing decisions, and the shared writing rules. Follow how_to_present to choose and research trends, compose one to three ideas (never padded), call record_shown_ideas, then show the pitch as ordinary chat text. If the member names or clearly refers to a particular trend to pitch, use get_trend_pitch instead, even if they say "today's pitch". Never use get_daily_drop. Extra words in a scheduled task do not mean inspect or repair the graph. Omit request_key and request_started_at to use the server's values; reuse a request key only to retry the same pull.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "request_key": { "type": "string", "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$", "description": "Optional: use a new lowercase UUID version 4 for a deliberate next pull. Reuse it only to retry that same pull." }, "member_local_date": { "type": "string", "description": "The member's local calendar date in YYYY-MM-DD form. Omit it when unknown." }, "request_started_at": { "type": "string", "description": "Optional current UTC time as YYYY-MM-DDTHH:mm:ss.sssZ. Omit it to use the server clock; never run code to make a timestamp." } }, "additionalProperties": false }arguments 20 linessearch_payday unknown never probed
For a pitch on a chosen trend, use get_trend_pitch directly; for the regular pitch use get_my_briefing. Use search_payday for other market questions or to find a trend or business whose identity is not yet known. Pass the member's phrase and useful synonyms. Returns the tracked phrase that matched, its figure when it clears the publishing floor, the trend and businesses paid nearby, and `individual_trends`: the individual trends on the site (each with its theme, monthly searches, growth and page) whose names match, best first; pass an individual trend's slug to get_trend. On a miss it returns only genuinely nearby trends. Never fill a gap from memory or web search. On a member connection, each call uses one of this membership's 400 daily data-tool calls, including a call whose lookup later errors. The allowance resets at midnight UTC; the regular pitch never uses it. The durable usage counter is updated and usage entries older than 31 days may be deleted. An allowance or ledger error returns no Payday AI data; its result explains the unavailability.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "terms" ], "properties": { "terms": { "type": "array", "items": { "type": "string" }, "description": "candidate search terms the agent derived from the user question" } }, "additionalProperties": false }arguments 17 linesget_company unknown never probed
Pass one business slug from search_payday. Returns everything Payday AI publishes on that business: sourced money figures, claims, shape, growth moves, tactics and public Payday AI links. Internal notes, audit fields and confidence values stay private. On a member connection, each call uses one of this membership's 400 daily data-tool calls, including a call whose lookup later errors. The allowance resets at midnight UTC; the regular pitch never uses it. The durable usage counter is updated and usage entries older than 31 days may be deleted. An allowance or ledger error returns no Payday AI data; its result explains the unavailability.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "the business slug from search_payday" } }, "additionalProperties": false }arguments 14 linessave_reaction unknown never probed
Call when the member answers an idea. Use yes for yes, interested, save it or maybe later: Saved. "Tell me more" is not a yes: send no reaction, so the idea stays in New, and tell them more. Use build_now when starting now: Building; no for rejection with their reason. Existing answers keep their column unless the member starts or requests a move. Record "build now" and "try this small test" as `build_now` (Building), "plan a fuller build" as `yes` (Saved), "no and why" as `no` (Rejected); `reason` holds their words and review date; "another idea" stays in New with no reaction saved, then pitch a new idea. If the idea is not saved on the board yet, save it again first with record_shown_ideas and the kept pitch using the same pull_id and links. Never use a reaction to put an idea on the board. Pass the stable idea id when record_shown_ideas returned one, plus the exact idea words and the member's reason. Payday AI records the answer on the member's board, keeps the reason on a rejection and clears an old rejection reason on approval. It refuses a rejection on an idea the member has launched, is earning from or has put in Sunset, and any answer on an idea they deleted; tell them to move it to Sunset or delete it on their board. Only when the member asks you in this chat to move one of their ideas to Saved or another column, call it with move_to instead of verdict. Only when they say yes to adding a business they already run that makes money, call it with existing_business true and move_to earning. Only when they ask you in this chat to link, unlink or change a trend, company or growth tactic on one of their ideas, call it with idea_id and link_change and nothing else, after reading the idea with graph and passing its links_at. Never do any of these on your own initiative or while composing a pitch, and tell them in one plain line what you did. Retrying the same answer changes nothing.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "user": { "type": "string", "maxLength": 200 }, "label": { "type": "string", "maxLength": 300, "minLength": 1, "description": "the idea's headline exactly as the customer saw it, never an internal id and never a directory business's own name — an idea is a business that does not exist yet. Shown back to them in their graph's Revenue tab." }, "detail": { "type": "string", "maxLength": 600, "description": "the one-line summary of the idea as the customer saw it" }, "reason": { "type": "string", "maxLength": 2000, "description": "the customer's one-line reason, in their words; with move_to, their own words asking for the move" }, "idea_id": { "type": "string", "maxLength": 128, "minLength": 1, "description": "the stable idea id returned by record_shown_ideas" }, "move_to": { "enum": [ "saved", "building", "launched", "earning", "sunset" ], "type": "string", "description": "only when the member asked you in this chat to move this idea to Saved or another column. Leave verdict out." }, "verdict": { "enum": [ "yes", "build_now", "no" ], "type": "string", "description": "the member's answer; leave it out when you send move_to" }, "link_change": { "type": "object", "required": [ "list", "action", "key", "links_at" ], "properties": { "to": { "anyOf": [ { "type": "string", "pattern": "^\\d{4}-(0[1-9]|1[0-2])$" }, { "type": "null" } ] }, "key": { "type": "string", "pattern": "^(gtt_[a-z0-9_]{1,60}|[a-z0-9][a-z0-9-]{0,80}(\\/[a-z0-9][a-z0-9-]{0,120})?)$" }, "from": { "anyOf": [ { "type": "string", "pattern": "^\\d{4}-(0[1-9]|1[0-2])$" }, { "type": "null" } ] }, "list": { "enum": [ "trends", "companies", "tactics" ], "type": "string" }, "action": { "enum": [ "add", "remove", "change", "move" ], "type": "string" }, "status": { "enum": [ "launch", "planned", "using", "stopped", "dropped" ], "type": "string" }, "links_at": { "anyOf": [ { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}\\.\\d{3}Z$" }, { "type": "null" } ] }, "position": { "type": "integer", "maximum": 12, "minimum": 1 } }, "description": "only when the member asked you in this chat to change the links on this idea: one change. list is trends, companies or tactics; action is add, remove, change (a tactic's status or months) or move; key is the trend or company slug or the gtt_ tactic id from Payday AI; a tactic you add or change needs status; links_at is the links_at from your latest graph read of this idea. Send idea_id with it and nothing else.", "additionalProperties": false }, "idea_reference": { "type": "string", "maxLength": 300, "minLength": 1, "description": "the idea headline; used when no stable idea id is available" }, "existing_business": { "type": "boolean", "description": "true only when the member said yes in this chat to adding a business they already run that makes money. Send move_to earning, label and detail, and no idea_id." } }, "additionalProperties": false }arguments 145 linesrecord_shown_ideas unknown never probed
Call once before showing your pitch, with every idea you will show, with scores and strengths and weaknesses. One to three ideas, highest score first; for a chosen-trend pitch, all on that same trend. The stored pull determines the scope. When every idea has a serious problem, save the highest-scoring idea without K1–K3, name its problem and say not to start until it is solved. Never present ideas excluded by the member's limits, dislikes or prior decisions, even reworded; if all candidates are excluded, follow the instructions' no-idea response and skip this call. Pass the exact pitch text and your workings. Payday AI checks them and returns the idea ids in the order shown. A retry with the same pull_id adds no cards. It only writes to the member's own private Payday AI board: it adds these ideas, or updates one already there when the same idea is shown again. It deletes nothing and sends nothing outside Payday AI.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "pull_id", "ideas" ], "properties": { "by": { "enum": [ "claude", "chatgpt", "assistant" ], "type": "string", "description": "optional: the agent app you run in, as one of the listed values, or 'assistant' when it is none of them. Left out, Payday AI records 'assistant'" }, "ideas": { "type": "array", "items": { "type": "object", "required": [ "headline", "body", "why_it_fits", "references" ], "properties": { "body": { "type": "string", "maxLength": 4000, "minLength": 1, "description": "the rest of the idea as you will show it, 4,000 characters at most; the board card keeps its opening" }, "proof": { "type": "object", "required": [ "business_is_paid_for", "keeps", "buyer_source", "adds_human_step" ], "properties": { "keeps": { "type": "array", "items": { "enum": [ "buyer", "job", "mechanism", "earning" ], "type": "string" }, "maxItems": 4, "description": "which of buyer, job, mechanism and earning the idea keeps from the chosen business, answered as the four questions in the idea rule" }, "buyer_source": { "type": "string", "maxLength": 200, "minLength": 1, "description": "\"search_phrase\" for the people searching this briefing's phrase, or \"company:<slug>\" for the buyers of a business on this briefing's shortlist" }, "adds_human_step": { "type": "boolean", "description": "true when the idea puts a person into the product to check each customer's work" }, "human_step_basis": { "enum": [ "business_does_same", "buyer_pays_for_judgement" ], "type": "string", "description": "when adds_human_step is true: the chosen business does the same, or the buyer is paying for that person's judgement" }, "human_step_evidence": { "type": "string", "maxLength": 400, "description": "when human_step_basis is business_does_same: the words of the chosen business's what_it_is, copied exactly, that say a person does this work for each customer" }, "business_is_paid_for": { "type": "string", "maxLength": 400, "minLength": 1, "description": "one clause: who pays the chosen business, for what outcome, how it works and how it earns" } }, "description": "your answers to the money test in the idea rule, for this idea. Payday AI keeps them with the idea", "additionalProperties": false }, "title": { "type": "string", "maxLength": 120, "minLength": 1, "description": "2 to 6 plain words describing what it sells and to whom; no invented name, filler, hype, numbers, colons, question marks or exclamation marks" }, "headline": { "type": "string", "maxLength": 300, "minLength": 1, "description": "the specific thing the member would make and who pays for it -- never the name of a business Payday AI already tracks" }, "references": { "type": "object", "required": [ "trend", "companies", "growth_tactics" ], "properties": { "trend": { "type": "string", "minLength": 1, "description": "the trend slug this idea leans on" }, "companies": { "type": "array", "items": { "type": "string", "minLength": 1 }, "description": "company slugs this idea cites, its example business first; empty only when this trend’s pack has no businesses and matching payment evidence is recorded in the workings and research_log" }, "growth_tactics": { "type": "array", "items": { "type": "string" }, "description": "the ids of the one or two growth tactics linked in How you'd grow, in the order written; the member's board shows them under How you grow" } }, "additionalProperties": false }, "why_it_fits": { "type": "string", "maxLength": 1000, "minLength": 1, "description": "names the member's own confirmed graph entries this idea leans on" }, "company_slug": { "type": "string", "description": "the example business this idea stands on; two ideas in one call never share one, and a repeat on this business only merges into an existing card when its headline also matches (folded)" } }, "additionalProperties": false }, "maxItems": 3, "minItems": 1, "description": "One to three ideas, highest score first; for a chosen-trend pitch, all on that same trend. The stored pull determines the scope. When all have serious problems, save the highest-scoring idea without K1–K3, its problem and why it must be solved before starting; if all candidates have K1–K3, skip this call" }, "pull_id": { "type": "string", "maxLength": 200, "minLength": 1, "description": "The pull_id from the get_my_briefing or get_trend_pitch response this pitch was written from." }, "workings": { "type": "object", "properties": { "sums": { "type": "array", "items": { "type": "object", "properties": { "share": { "type": "number" }, "period": { "type": "string" }, "price_usd": { "type": "number" }, "usd_month": { "type": "number" }, "base_rough": { "type": "number" }, "candidate_label": { "type": "string" }, "customers_realistic": { "type": "number" } }, "additionalProperties": true } }, "closest": { "type": "object", "properties": { "why_not": { "type": "array", "items": { "type": "string" } }, "candidate_label": { "type": "string" } }, "description": "Legacy field; omit. It has no effect on selection or presentation.", "additionalProperties": true }, "examples": { "type": "array", "items": { "type": "object", "properties": { "sheet": { "type": "object", "properties": {}, "additionalProperties": true }, "sources": { "type": "array", "items": { "type": "string" } }, "trend_slug": { "type": "string" }, "company_slug": { "type": "string" } }, "additionalProperties": true } }, "candidates": { "type": "array", "items": { "type": "object", "properties": { "kill": { "type": "string", "description": "K1 to K8, or null" }, "label": { "type": "string" }, "scores": { "type": "object", "properties": { "pay": { "$ref": "#/properties/workings/properties/candidates/items/properties/scores/properties/demand" }, "edge": { "$ref": "#/properties/workings/properties/candidates/items/properties/scores/properties/demand" }, "sums": { "$ref": "#/properties/workings/properties/candidates/items/properties/scores/properties/demand" }, "demand": { "type": "number", "maximum": 3, "minimum": 0 }, "first_100": { "$ref": "#/properties/workings/properties/candidates/items/properties/scores/properties/demand" }, "difference": { "$ref": "#/properties/workings/properties/candidates/items/properties/scores/properties/demand" } }, "additionalProperties": true }, "way_in": { "enum": [ "your_market", "new_buyer", "one_feature", "ai_rebuild", "buyer_tools", "reimagined", "no_code" ], "type": "string" }, "lame_no": { "type": "array", "items": { "type": "number" } }, "reasons": { "type": "object", "properties": {}, "additionalProperties": true }, "ai_covers": { "type": "array", "items": { "type": "object", "properties": { "gap": { "type": "string" }, "how": { "type": "string" } }, "additionalProperties": true } }, "divergence": { "type": "array", "items": { "type": "object", "properties": { "differs_in": { "enum": [ "buyer", "paid_for", "both" ], "type": "string" }, "from_label": { "type": "string" } }, "additionalProperties": true } }, "shown_rank": { "type": "number", "description": "1, 2 or 3 in the order shown, or null" }, "trend_slug": { "type": "string" }, "failed_check": { "enum": [ "demand", "gap" ], "type": "string", "description": "the step 6 check that dropped it, or null" }, "strengths_used": { "type": "array", "items": { "type": "string" } }, "payment_evidence": { "type": "object", "properties": { "price": { "type": "string" }, "pays_for": { "type": "string" }, "who_pays": { "type": "string" }, "source_url": { "type": "string" } }, "additionalProperties": true }, "growth_tactic_ids": { "type": "array", "items": { "type": "string" } }, "example_company_slug": { "type": "string" } }, "additionalProperties": true }, "description": "every candidate you wrote, dropped ones included" }, "lead_trend": { "type": "object", "properties": { "why": { "type": "string" }, "trend_slug": { "type": "string" } }, "additionalProperties": true }, "member_card": { "type": "object", "properties": { "rate": { "type": "number" }, "limit_ids": { "type": "array", "items": { "type": "string" } }, "rate_date": { "type": "string" }, "preferences": { "type": "array", "items": { "type": "object", "properties": { "preference": { "type": "string" }, "from_decision_id": { "type": "string" } }, "additionalProperties": true } }, "strength_ids": { "type": "array", "items": { "type": "string" } }, "sections_read": { "type": "array", "items": { "type": "string" }, "description": "every section of the member's graph that has entries" }, "goal_usd_month": { "type": "number" } }, "additionalProperties": true }, "count_reason": { "type": "string" }, "none_cleared": { "type": "boolean" }, "research_log": { "type": "array", "items": { "type": "object", "properties": { "kind": { "enum": [ "search", "fetch" ], "type": "string" }, "found": { "type": "string" }, "changed": { "enum": [ "nothing", "killed_candidate", "changed_idea", "hard_part", "fact_check" ], "type": "string" }, "q_or_url": { "type": "string" }, "candidate_label": { "type": "string" } }, "additionalProperties": true }, "description": "one entry per lookup you made" }, "graph_question": { "enum": [ "soften", "strength", "interest" ], "type": "string", "description": "fixed code for the optional graph question asked; omit when none" }, "web_unavailable": { "type": "boolean" } }, "description": "your private workings for this pitch. Payday AI keeps them beside the pitch and never shows them to the member", "additionalProperties": true }, "pitch_text": { "type": "string", "maxLength": 8000, "description": "the full pitch exactly as you will show it" }, "none_cleared": { "type": "boolean", "description": "Legacy field; omit. It has no effect on scoring or presentation." } }, "additionalProperties": false }arguments 511 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id19525fdc382975df.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/19525fdc382975df/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/19525fdc382975df?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.