Skip to content
Back to search

daymaker

MarketplaceWorks with Claude CodeGitHubIncomplete

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/daymaker-hq/daymaker-for-agents with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/daymaker-hq/daymaker-for-agents'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/daymaker-hq--daymaker-for-agents/badge.svg)](/listings/daymaker-hq--daymaker-for-agents)

HTML

<a href="/listings/daymaker-hq--daymaker-for-agents"><img src="/api/listings/daymaker-hq--daymaker-for-agents/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Sign in (no key)

In Claude Code, install the plugin and sign in:

/plugin marketplace add daymaker-hq/daymaker-for-agents
/plugin install daymaker@daymaker
/mcp

`/plugin install` opens the plugin's details: choose where to install it. Then `/mcp` lists the `daymaker` server; choose it and sign in to Daymaker. Other plugin systems:

devin plugins install daymaker-hq/daymaker-for-agents                          # Devin
agy plugin install https://github.com/daymaker-hq/daymaker-for-agents          # Antigravity

A client that implements Agent Plugins 1.0 loads the root `plugin.json` and `mcp.json`. Without a plugin, add the server URL `https://daymaker.com/mcp` to your client and sign in when it asks; the table below has each client's steps.

Then ask:

> Who in my Daymaker leads has a gift ready to send?

Use an API key

Make a key in Daymaker under **Settings, API and MCP** (<https://daymaker.com/autopilot/settings/api-and-mcp>). Keys start with `dmk_live_`. When you make one you choose what it may do:

| In the app | Scopes | It can | | ---------- | ------ | ------ | | Read only | `read` | See leads, campaigns, orders, the pipeline, signals and prices | | Read and work | `read`, `work` | Also add leads, start research and gift searches (these use credits), pick gifts, write notes and change campaigns | | Full access | `read`, `work`, `send` | Also send gift links, make payment pages, reach out by email and LinkedIn, and post public replies, all in your name |

A key acts as the person who made it. Keep it on a server or in your own environment: a key in a browser or an app is a key anyone can use.

export DAYMAKER_KEY=dmk_live_...
npx -y @daymaker/mcp          # the local MCP server, on stdin and stdout (Node 22 or newer)

Your MCP client starts that command for you; see the table below. From your own code:

npm install @daymaker/sdk
import { DaymakerClient } from "@daymaker/sdk";

const dm = new DaymakerClient(); // reads DAYMAKER_KEY

const me = await dm.getMe();
console.log(me.you?.email, me.credits?.balance);

const { leads } = await dm.listLeads({ tab: "gift_ready", limit: 10 });
for (const lead of leads) console.log(lead.lead_id, lead.name);

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 25 lines
  1. {
  2. "name": "daymaker",
  3. "owner": {
  4. "name": "Daymaker",
  5. "email": "contact@daymaker.com"
  6. },
  7. "metadata": {
  8. "description": "Daymaker plugins for Claude Code",
  9. "version": "0.4.1"
  10. },
  11. "plugins": [
  12. {
  13. "name": "daymaker",
  14. "source": "./plugins/daymaker",
  15. "description": "Research leads, pick gifts and send them through the Daymaker MCP server. Sign in with your Daymaker account.",
  16. "category": "productivity",
  17. "keywords": [
  18. "daymaker",
  19. "gifts",
  20. "leads",
  21. "outreach"
  22. ]
  23. }
  24. ]
  25. }
README.md · README · 255 lines
  1. # Daymaker for agents
  2. [Daymaker](https://daymaker.com) finds people worth reaching, researches what they care about, picks gifts they would love, and sends them. This repository connects your agent to it: plugins for Claude Code and other agent clients, a local MCP server, and a typed TypeScript SDK for the [Daymaker API](https://daymaker.com/api/v2/docs).
  3. Everything here runs on your side and calls the Daymaker API or the hosted Daymaker MCP server.
  4. | Piece | What it is | Use it when |
  5. | ----- | ---------- | ----------- |
  6. | Hosted MCP server | `https://daymaker.com/mcp`. You sign in to Daymaker from your client; there is no key to manage | Your client can sign in to an MCP server. Start here. |
  7. | Plugins | Claude Code (`plugins/daymaker/`), Devin (`.devin-plugin/`), Antigravity (`.antigravity-plugin/`) and Agent Plugins 1.0 (`plugin.json`), each with the hosted server and the `daymaker` skill | You want Daymaker installed as a plugin |
  8. | [`@daymaker/mcp`](packages/mcp) | A local MCP server (stdio) with one tool per API operation, using an API key | Your client cannot sign in to the hosted server, or you want a key with a narrow scope |
  9. | [`@daymaker/sdk`](packages/sdk) | A typed TypeScript client for the Daymaker API | You are writing your own agent or backend |
  10. Whichever way you connect, the agent acts as you in your own Daymaker workspace: your role, your team's limits and your credits apply, exactly as in the app.
  11. ## Quickstart
  12. ### Sign in (no key)
  13. In Claude Code, install the plugin and sign in:
  14. ```text
  15. /plugin marketplace add daymaker-hq/daymaker-for-agents
  16. /plugin install daymaker@daymaker
  17. /mcp
  18. ```
  19. `/plugin install` opens the plugin's details: choose where to install it. Then `/mcp` lists the `daymaker` server; choose it and sign in to Daymaker. Other plugin systems:
  20. ```text
  21. devin plugins install daymaker-hq/daymaker-for-agents # Devin
  22. agy plugin install https://github.com/daymaker-hq/daymaker-for-agents # Antigravity
  23. ```
  24. A client that implements Agent Plugins 1.0 loads the root `plugin.json` and `mcp.json`. Without a plugin, add the server URL `https://daymaker.com/mcp` to your client and sign in when it asks; the table below has each client's steps.
  25. Then ask:
  26. > Who in my Daymaker leads has a gift ready to send?
  27. ### Use an API key
  28. Make a key in Daymaker under **Settings, API and MCP** (<https://daymaker.com/autopilot/settings/api-and-mcp>). Keys start with `dmk_live_`. When you make one you choose what it may do:
  29. | In the app | Scopes | It can |
  30. | ---------- | ------ | ------ |
  31. | Read only | `read` | See leads, campaigns, orders, the pipeline, signals and prices |
  32. | Read and work | `read`, `work` | Also add leads, start research and gift searches (these use credits), pick gifts, write notes and change campaigns |
  33. | Full access | `read`, `work`, `send` | Also send gift links, make payment pages, reach out by email and LinkedIn, and post public replies, all in your name |
  34. A key acts as the person who made it. Keep it on a server or in your own environment: a key in a browser or an app is a key anyone can use.
  35. ```bash
  36. export DAYMAKER_KEY=dmk_live_...
  37. npx -y @daymaker/mcp # the local MCP server, on stdin and stdout (Node 22 or newer)
  38. ```
  39. Your MCP client starts that command for you; see the table below. From your own code:
  40. ```bash
  41. npm install @daymaker/sdk
  42. ```
  43. ```ts
  44. import { DaymakerClient } from "@daymaker/sdk";
  45. const dm = new DaymakerClient(); // reads DAYMAKER_KEY
  46. const me = await dm.getMe();
  47. console.log(me.you?.email, me.credits?.balance);
  48. const { leads } = await dm.listLeads({ tab: "gift_ready", limit: 10 });
  49. for (const lead of leads) console.log(lead.lead_id, lead.name);
  50. ```
  51. ## Connect your client
  52. <!-- agents:start -->
  53. Sign in: the client adds `https://daymaker.com/mcp` and signs you in to Daymaker, with no key. API key: the client starts the local server (`npx -y @daymaker/mcp`), which reads `DAYMAKER_KEY`.
  54. | Client | Sign in | API key for the local server | Example |
  55. | ------ | ------- | ---------------------------- | ------- |
  56. | Claude Code | yes | `DAYMAKER_KEY` from the environment | [`.mcp.json`](examples/agents/claude-code/.mcp.json), [`mcp.local.json`](examples/agents/claude-code/mcp.local.json) |
  57. | Claude (claude.ai and Claude Desktop) | yes | pasted into the file | [`claude_desktop_config.json`](examples/agents/claude/claude_desktop_config.json) |
  58. | ChatGPT | yes | no local server | none |
  59. | Codex CLI | yes | `DAYMAKER_KEY` from the environment | [`config.toml`](examples/agents/codex/config.toml) |
  60. | VS Code (Copilot) | yes | `DAYMAKER_KEY` from the environment | [`.mcp.json`](examples/agents/vscode/.mcp.json), [`mcp.local.json`](examples/agents/vscode/mcp.local.json) |
  61. | Gemini CLI | yes | `DAYMAKER_KEY` from the environment | [`settings.json`](examples/agents/gemini-cli/settings.json), [`settings.local.json`](examples/agents/gemini-cli/settings.local.json) |
  62. | OpenCode | yes | `DAYMAKER_KEY` from the environment | [`opencode.json`](examples/agents/opencode/opencode.json) |
  63. | Cursor | not yet | `DAYMAKER_KEY` from the environment | [`mcp.json`](examples/agents/cursor/mcp.json) |
  64. | Devin Desktop (formerly Windsurf), Cascade | not tested yet | `DAYMAKER_KEY` from the environment | [`mcp_config.json`](examples/agents/devin-desktop/mcp_config.json) |
  65. | Cline | not tested yet | pasted into the file | [`cline_mcp_settings.json`](examples/agents/cline/cline_mcp_settings.json) |
  66. | Any other MCP client | yes | `DAYMAKER_KEY` from the environment | [`mcp.json`](examples/agents/other/mcp.json) |
  67. - **Claude Code.** Where: the plugin, the command below, or `.mcp.json` in the project root. The first two lines are typed inside Claude Code and install the plugin: the hosted server plus the `daymaker` skill. The third adds only the server. Either way, type `/mcp` and sign in to Daymaker. `mcp.local.json` is the local server with a key instead: copy its entry into `.mcp.json`. Docs: <https://code.claude.com/docs/en/mcp>
  68. ```text
  69. /plugin marketplace add daymaker-hq/daymaker-for-agents
  70. /plugin install daymaker@daymaker
  71. claude mcp add --transport http --scope user daymaker https://daymaker.com/mcp
  72. ```
  73. - **Claude (claude.ai and Claude Desktop).** Where: Customize, then Connectors. The connector takes the server URL and signs you in. `claude_desktop_config.json` is for the local server in Claude Desktop: that file starts local servers only, and they get only a few variables from your environment, so the example carries a pasted key. Docs: <https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp>
  74. ```text
  75. Customize > Connectors > Add > Add custom connector > a name and https://daymaker.com/mcp > Continue > Add > Connect > sign in to Daymaker
  76. ```
  77. - **ChatGPT.** Where: Plugins, in ChatGPT on the web (chatgpt.com/plugins). No file to edit. Docs: <https://developers.openai.com/api/docs/guides/custom-mcp-server>
  78. ```text
  79. chatgpt.com/plugins > + > Add custom MCP server > a name > Server URL https://daymaker.com/mcp > authentication: OAuth > I understand and want to continue > Create as a plugin > Install > Connect > sign in to Daymaker
  80. ```
  81. - **Codex CLI.** Where: `~/.codex/config.toml` (or `.codex/config.toml` in a trusted project). `codex mcp login` opens the Daymaker sign-in. The second block of the file is the local server: `env_vars` passes `DAYMAKER_KEY` through from your shell. Docs: <https://developers.openai.com/codex/mcp>
  82. ```text
  83. codex mcp add daymaker --url https://daymaker.com/mcp
  84. codex mcp login daymaker
  85. ```
  86. - **VS Code (Copilot).** Where: `.mcp.json` in the workspace root, or `~/.copilot/mcp-config.json`. The top-level key is `mcpServers`. VS Code asks you to sign in to Daymaker when the server starts. `mcp.local.json` is the local server: copy its entry into `.mcp.json`. VS Code fills in `${DAYMAKER_KEY}` from the environment it was started from. The older `.vscode/mcp.json` (top-level key `servers`) still loads, but VS Code has deprecated it, and a key asked for there with `${input:...}` does not reach Copilot sessions. Docs: <https://code.visualstudio.com/docs/agents/reference/mcp-configuration>
  87. ```text
  88. Install link: https://vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522daymaker%2522%252C%2522type%2522%253A%2522http%2522%252C%2522url%2522%253A%2522https%253A%252F%252Fdaymaker.com%252Fmcp%2522%257D
  89. ```
  90. - **Gemini CLI.** Where: `~/.gemini/settings.json` or `.gemini/settings.json` in the project. `httpUrl` selects Streamable HTTP; `url` would mean the older SSE transport. The second line is typed inside Gemini CLI and opens the Daymaker sign-in. `settings.local.json` is the local server: copy its entry into `settings.json`. Gemini CLI fills in `$DAYMAKER_KEY` from your shell. Docs: <https://geminicli.com/docs/tools/mcp-server/>
  91. ```text
  92. gemini mcp add --transport http daymaker https://daymaker.com/mcp
  93. /mcp auth daymaker
  94. ```
  95. - **OpenCode.** Where: `opencode.json` in the project or `~/.config/opencode/opencode.json`. The command opens the Daymaker sign-in for the `remote` entry. The `local` entry is the local server; OpenCode's variable syntax is `{env:NAME}` without a dollar sign. Keep the one you use. The file is in the shape both OpenCode 1 and 2 read. Docs: <https://opencode.ai/docs/mcp-servers/>
  96. ```text
  97. opencode mcp auth daymaker
  98. ```
  99. - **Cursor.** Where: `.cursor/mcp.json` in the project or `~/.cursor/mcp.json`. Use the local server. When Cursor registers with a hosted server it lists a `cursor://` return address next to its web and localhost ones, and Daymaker's sign-in refuses that registration for now. Cursor fills in `${env:DAYMAKER_KEY}` from the environment it was started from. Docs: <https://cursor.com/docs/mcp>
  100. - **Devin Desktop (formerly Windsurf), Cascade.** Where: the file Cascade's `Open MCP config file` opens: `~/.config/devin/mcp_config.json`, or `%AppData%/devin/mcp_config.json` on Windows. The local server, which works with a key. Cascade fills in `${env:DAYMAKER_KEY}` from the environment. Press refresh in the MCPs panel after editing. Cascade can also sign in to hosted servers, but Daymaker has not tested its sign-in yet. Docs: <https://docs.devin.ai/windsurf/plugins/cascade/mcp>
  101. - **Cline.** Where: `cline_mcp_settings.json` (the MCP Servers icon, then Configure, then Configure MCP Servers). The local server, which works with a key. Replace the placeholder with your key; the file is not in your repository. Cline can also sign in to hosted servers, but Daymaker has not tested its sign-in yet. Docs: <https://docs.cline.bot/mcp/mcp-overview>
  102. - **Any other MCP client.** Where: your client's MCP server settings. The common `mcpServers` shape with both ways in; keep the one you use and map its fields to your client's format. The hosted entry works in a client that signs in to MCP servers and returns to a web address or to this computer. In any other client, use the local entry. If your client does not fill in `${DAYMAKER_KEY}`, paste the key there. Docs: <https://modelcontextprotocol.io/docs/getting-started/intro>
  103. <!-- agents:end -->
  104. Daymaker tests the Claude Code plugin. The Devin, Antigravity and Agent Plugins manifests follow each system's published format; if a sign-in does not complete in your client, use the local server with an API key and tell us at [contact@daymaker.com](mailto:contact@daymaker.com).
  105. ## The local MCP server
  106. `@daymaker/mcp` gives your client one tool per Daymaker API operation. It needs Node 22 or newer.
  107. ```bash
  108. DAYMAKER_KEY=dmk_live_... npx -y @daymaker/mcp
  109. ```
  110. Or without npm, the single-file build in this repository:
  111. ```bash
  112. git clone https://github.com/daymaker-hq/daymaker-for-agents && cd daymaker-for-agents
  113. DAYMAKER_KEY=dmk_live_... node bin/daymaker-mcp.mjs
  114. ```
  115. Or with Docker: `docker build -t daymaker-mcp . && docker run -i --rm -e DAYMAKER_KEY daymaker-mcp`.
  116. | Environment variable | Default | Meaning |
  117. | -------------------- | ------- | ------- |
  118. | `DAYMAKER_KEY` | (required) | Your API key, `dmk_live_...` |
  119. | `DAYMAKER_API_URL` | `https://daymaker.com/api/v2` | The API's address. Leave it alone unless Daymaker gives you another |
  120. | `DAYMAKER_MCP_READ_ONLY` | unset | `1` offers only the tools that change nothing: reads and price checks |
  121. | `DAYMAKER_MCP_SCOPES` | unset | A comma list of `read`, `work`, `send`: offers only the tools those scopes reach |
  122. The tools the server lists do not depend on your key. A tool your key's scopes do not reach answers `insufficient_scope` and names the scope it needs. Set `DAYMAKER_MCP_SCOPES` to your key's scopes to hide those tools.
  123. <!-- tools:start -->
  124. 30 tools, one per Daymaker API operation. A tool's name is the snake_case of its SDK method.
  125. | Tool | SDK method | Route | Scope | What it does | Notes |
  126. | ---- | ---------- | ----- | ----- | ------------ | ----- |
  127. | `get_me` | `getMe` | `GET /me` | read | Your workspace | |
  128. | `list_leads` | `listLeads` | `GET /leads` | read | List leads | |
  129. | `add_leads` | `addLeads` | `POST /leads` | work | Add leads | can use credits, takes an Idempotency-Key |
  130. | `get_lead` | `getLead` | `GET /leads/{lead_id}` | read | Get a lead | |
  131. | `research_lead` | `researchLead` | `POST /leads/{lead_id}/research` | work | Research a lead | can use credits, takes an Idempotency-Key |
  132. | `find_work_email` | `findWorkEmail` | `POST /leads/{lead_id}/work-email` | work | Find a lead's work email | takes an Idempotency-Key |
  133. | `find_gifts` | `findGifts` | `POST /leads/{lead_id}/gift-search` | work | Find gift ideas | can use credits, takes an Idempotency-Key |
  134. | `choose_gift` | `chooseGift` | `PUT /leads/{lead_id}/gift` | work | Choose a gift | takes an Idempotency-Key |
  135. | `clear_gift` | `clearGift` | `DELETE /leads/{lead_id}/gift` | work | Take the pick back | takes an Idempotency-Key |
  136. | `set_gift_message` | `setGiftMessage` | `PUT /leads/{lead_id}/gift-message` | work | Write the gift's note | takes an Idempotency-Key |
  137. | `list_campaigns` | `listCampaigns` | `GET /campaigns` | read | List campaigns | |
  138. | `create_campaign` | `createCampaign` | `POST /campaigns` | work | Create a campaign | takes an Idempotency-Key |
  139. | `get_campaign` | `getCampaign` | `GET /campaigns/{campaign_id}` | read | Get a campaign | |
  140. | `update_campaign` | `updateCampaign` | `PATCH /campaigns/{campaign_id}` | work | Change a campaign | takes an Idempotency-Key |
  141. | `review_send` | `reviewSend` | `POST /campaigns/{campaign_id}/send-review` | read | Review a send | |
  142. | `quote_gift_links` | `quoteGiftLinks` | `POST /campaigns/{campaign_id}/gift-links/quote` | read | Price gift links | |
  143. | `send_gift_links` | `sendGiftLinks` | `POST /campaigns/{campaign_id}/gift-links` | send | Send gift links | sends in your name, Idempotency-Key required |
  144. | `quote_checkout` | `quoteCheckout` | `POST /campaigns/{campaign_id}/checkout/quote` | read | Price a shipped send | |
  145. | `create_checkout` | `createCheckout` | `POST /campaigns/{campaign_id}/checkout` | send | Make a payment page for a shipped send | sends in your name, Idempotency-Key required |
  146. | `quote_reach_out` | `quoteReachOut` | `POST /campaigns/{campaign_id}/reach-out/quote` | read | Price Reach out | |
  147. | `reach_out` | `reachOut` | `POST /campaigns/{campaign_id}/reach-out` | send | Reach out with a gift | sends in your name, Idempotency-Key required |
  148. | `quote_purchase_checkout` | `quotePurchaseCheckout` | `POST /purchases/{purchase_id}/checkout/quote` | read | Price claimed gifts and yeses | |
  149. | `create_purchase_checkout` | `createPurchaseCheckout` | `POST /purchases/{purchase_id}/checkout` | send | Make a payment page for claimed gifts and yeses | sends in your name, Idempotency-Key required |
  150. | `sync_purchase` | `syncPurchase` | `POST /purchases/{purchase_id}/sync` | send | Check and finish a purchase | sends in your name |
  151. | `set_gift_outcome` | `setGiftOutcome` | `PUT /purchases/{purchase_id}/leads/{lead_id}/outcome` | work | Record what happened after a gift | takes an Idempotency-Key |
  152. | `list_orders` | `listOrders` | `GET /orders` | read | List orders | |
  153. | `get_pipeline` | `getPipeline` | `GET /pipeline` | read | The pipeline | |
  154. | `list_signals` | `listSignals` | `GET /signals` | read | List signals | |
  155. | `decide_signal` | `decideSignal` | `POST /signals/{signal_id}/decision` | work | Sort a signal | takes an Idempotency-Key |
  156. | `reply_to_signal` | `replyToSignal` | `POST /signals/{signal_id}/reply` | send | Reply to a signal | sends in your name, Idempotency-Key required |
  157. <!-- tools:end -->
  158. The hosted server at `https://daymaker.com/mcp` has its own tool list, curated for agents, with a few things the API does not have yet. Its list can change on Daymaker's side; your client shows the current one.
  159. ## The SDK
  160. - **One method per operation**, named by the contract's `operationId` (`dm.listLeads`, `dm.researchLead`, `dm.sendGiftLinks`, ...). The input is one flat object: path, query and body fields side by side. Methods return the answer's body; `dm.request(id, input)` returns `{ data, status, requestId, idempotencyKey, idempotentReplay, attempts }`.
  161. - **Types** for every input and answer come from the published contract ([`spec/openapi.json`](spec/openapi.json), served at `https://daymaker.com/api/v2/openapi.json`). A field with nothing in it is left out of an answer, so read a missing field as empty.
  162. - **Lists.** `dm.pages("listLeads", { limit: 100 })` is an async iterator that follows `next_offset` to the end. A page can hold fewer than `limit`, so always continue from `next_offset`.
  163. - **Idempotency.** Every write that takes an `Idempotency-Key` gets one: yours (`idempotency_key`), or a fresh UUID that the SDK reuses across its own retries. Once a request with a key has done something, a retry with the same key gets that first answer back (`idempotentReplay: true`) instead of acting twice. Daymaker keeps a key's answer for 24 hours.
  164. - **Retries** (2 by default; `maxRetries` changes it). Timeouts, network errors and `500`, `502`, `503`, `504` are retried only where that is safe: a read, a price check, or a write that carries an `Idempotency-Key`. A `429` is waited out when its `Retry-After` is 30 seconds or less, and `409 idempotency_in_flight` (the first request with that key is still running) is waited out with the same key. `outcome_unknown`, `partially_done` and `in_progress` are never retried: the request may have acted, so check what was done first, and use a new key if you then send again. Redirects are never followed.
  165. - **Errors** are `DaymakerError` with `status`, `code`, `message`, `requestId`, `fields`, `details` (everything the API said, such as `new_quote` or `needs`), `retryAfterMs` and `idempotencyKey`. Branch on `status` and `code`; `message` is for people and may change. Quote `requestId` when you ask Daymaker about a request.
  166. ## Sending safely
  167. Sending is real money and real messages in your name, and it cannot be taken back. The API lets you show a person the price before a gift goes out:
  168. 1. **Price it first.** Each gift send has a price check that sends nothing and charges nothing: `quoteGiftLinks`, `quoteCheckout`, `quotePurchaseCheckout`, `quoteReachOut`. A public reply (`replyToSignal`) has none: show the person the exact words first.
  169. 2. **Show the person** who gets what and what it costs, and get a yes.
  170. 3. **Send the same selection** with the quote's `quote_revision`, and `total_usd` for a payment page. Reach out takes `total_usd` only: the quote's `total_if_all_say_yes_usd`. If the price or the selection moved, the answer is `409 quote_changed` with the new price: show it and ask again.
  171. ```ts
  172. const leads = [{ lead_id: "lead_1", how: "email_link" as const }];
  173. const { quote } = await dm.quoteGiftLinks({ campaign_id: "camp_1", leads });
  174. // ...show `quote.lines` and `quote.total_if_all_claimed_usd` to the person and wait for a yes...
  175. const sent = await dm.request("sendGiftLinks", { campaign_id: "camp_1", leads, quote_revision: quote.quote_revision! });
  176. console.log(sent.status, sent.idempotencyKey); // keep the key: sending it again cannot send twice
  177. ```
  178. A payment page is paid by a person, an owner or admin of the workspace, on Stripe. Nothing is charged until they pay. After they pay, `syncPurchase` finishes the purchase.
  179. For an agent, the safest setup is a key that cannot send at all (Read only, or Read and work), or `DAYMAKER_MCP_READ_ONLY=1` on the local server. On the local server every tool outside the `read` scope is marked `destructiveHint`, the tools that send say so in their description, and each of them needs an `idempotency_key` that the model makes up before the call, so a call that is repeated because its answer was lost cannot send twice.
  180. ## Limits and errors
  181. Each key may make 120 requests a minute, and each person 240 a minute across their keys. Research, gift searches and sends have the same per-person limits as in the app. Over a limit the API answers `429` with `Retry-After`.
  182. Errors are JSON: `{ "error": { "code", "message", "request_id", ... } }`. `400` is a problem with the request (`fields` says where), `401` a missing or invalid key, `402` not enough credits, `403` a scope or a role the key does not have, `404` nothing by that id in your workspace, `409` a state that moved (a price, a payment page being made, work already under way), `422` understood but not done (over `max_credits`, a lead missing what the send needs, a refusal), `429` a limit, `502` a change whose end Daymaker could not confirm (`outcome_unknown`: check before trying again). The full list of codes is in the [API reference](https://daymaker.com/api/v2/docs).
  183. ## What is not possible yet
  184. - **The hosted server takes a sign-in, not an API key.** For a key, use the local server or the SDK.
  185. - **Cursor cannot sign in to the hosted server yet.** Use the local server in Cursor.
  186. - **The two servers have different tool lists.** The hosted one is curated by Daymaker and has a few things the API does not have yet; the local one is exactly the API.
  187. - **No test mode for writes.** Every `dmk_live_` key works in your real workspace. Give an agent a Read only key while you try things out.
  188. Looking for cakes? The Cold Caked Cake API is a different API with its own keys (`dm_live_`, `dm_test_`): <https://coldcaked.com/docs/api>. Those keys do not work here, and Daymaker keys do not work there.
  189. ## Contributing
  190. Issues and pull requests: <https://github.com/daymaker-hq/daymaker-for-agents>. Build and test with `npm ci && npm run build && npm run typecheck && npm test`. `npm run test:e2e` checks the hosted server's sign-in documents, the example files and the local server, with no key. The files under `examples/agents/`, the client table above and the two files under `plugins/daymaker/` that copy the root's skill and `.mcp.json` are generated by `npm run agents`.
  191. ## License
  192. Proprietary and source-visible, for use with Daymaker's services under the [Daymaker Terms](https://daymaker.com/terms). See [LICENSE](LICENSE). The single-file build `bin/daymaker-mcp.mjs` contains open-source packages under their own licenses: see [THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.