Tag: Claude AI

  • Claude for Nonprofits: Discounts, Eligibility & Use Cases (2026)

    Claude for Nonprofits: Discounts, Eligibility & Use Cases (2026)

    Claude for Nonprofits is Anthropic’s program that gives qualifying nonprofits up to 75% off Claude’s Team and Enterprise plans — with Team seats starting around $8 per user per month — plus nonprofit-specific data connectors, free AI training, and access to a $150M fellowship. If your organization holds 501(c)(3) status (or an international equivalent), you almost certainly qualify. Here’s what’s included, who’s eligible, and how mission-driven teams are putting it to work.

    What is Claude for Nonprofits?

    Launched by Anthropic in 2026, Claude for Nonprofits packages the same Claude models used by enterprise teams into an offering built for the realities of mission-driven work: tight budgets, lean staff, and a constant need to do more with less. It bundles three things nonprofits rarely get together — steep pricing discounts, sector-specific integrations, and free training — into one program. It runs on the same foundation as Anthropic’s commercial plans, so nonprofits get the latest Claude models (Opus, Sonnet, and Haiku), not a stripped-down version.

    Who qualifies?

    Eligibility is broad, and Anthropic validates organizations through its partner Goodstack. The program covers:

    • 501(c)(3) nonprofits in the U.S., and organizations with equivalent charitable designations internationally
    • K–12 schools, public and private
    • Mission-based healthcare organizations with 501(c)(3) status — including independent Critical Access Hospitals (CAHs), Rural Emergency Hospitals (REHs), HRSA-designated Federally Qualified Health Centers (FQHCs) and FQHC Look-Alikes, and CMS-certified Rural Health Clinics (RHCs)

    If you can document charitable status, eligibility is usually straightforward.

    How much does it cost?

    Qualifying organizations receive up to 75% off Claude’s Team and Enterprise plans:

    • Team plan — discounted pricing starts around $8 per user, per month, which makes it realistic to roll Claude out to an entire staff rather than a single power user.
    • Enterprise plan — custom pricing for larger organizations; you contact Anthropic’s sales team.

    Both tiers include Claude’s current model lineup. Pricing and model availability change, so confirm the latest figures on Anthropic’s official Claude for Nonprofits announcement. Curious how discounted seats compare to standard rates? Run the numbers on our Claude pricing calculator.

    What nonprofits actually use Claude for

    The highest-leverage uses cluster around the work that eats the most staff time:

    • Grant writing — drafting proposals aligned to a specific funder’s priorities, then tailoring them per application.
    • Donor stewardship — personalizing outreach and acknowledgements at a scale a small development team could never manage by hand.
    • Program evaluation & impact analysis — turning messy program data into the impact narratives boards and funders want.
    • Board & compliance documentation — generating board materials, reports, and compliance documents from source data.

    The common thread: Claude removes the blank-page tax on the writing- and analysis-heavy work that keeps nonprofit staff at their desks instead of in the field.

    Connectors built for the nonprofit stack

    Anthropic built integrations with the platforms nonprofits already run on, so Claude can work against real organizational data:

    • Benevity — access to 2.4M+ validated organizations for volunteering and donation research
    • Blackbaud — CRM and fundraising tools for donor management, campaign tracking, and donation optimization
    • Candid — data on nonprofits and funders to discover organizations, grants, and philanthropic opportunities

    Free training and the Claude Corps fellowship

    Two things set this apart from a plain discount:

    • AI Fluency for Nonprofits — a free course Anthropic developed with GivingTuesday, covering grant writing, program evaluation, donor engagement, and organizational efficiency. It’s aimed at staff, not engineers.
    • Claude Corps — a $150M fellowship initiative pairing nonprofits with AI expertise and resources to implement Claude across their operations. Anthropic also works with partners including The Bridgespan Group, Idealist Consulting, Vera Solutions, and Slalom to support adoption.

    How to get started

    1. Confirm your charitable status (501(c)(3) or international equivalent).
    2. Apply through Anthropic’s nonprofit page — eligibility is validated via Goodstack.
    3. Choose Team (self-serve, discounted seats) or contact sales for Enterprise.
    4. Enroll staff in the free AI Fluency for Nonprofits course to get value quickly.

    Start at Claude for Nonprofits, or read Anthropic’s getting-started guide.

    Frequently asked questions

    Is Claude free for nonprofits?

    Not free, but heavily discounted — up to 75% off Team and Enterprise plans, with Team seats starting around $8 per user per month for qualifying organizations.

    Who qualifies for Claude for Nonprofits?

    501(c)(3) nonprofits (and international equivalents), K–12 public and private schools, and mission-based healthcare organizations with 501(c)(3) status. Eligibility is validated by Goodstack.

    Which Claude models do nonprofits get?

    The discounted plans include Claude’s current lineup — Opus, Sonnet, and Haiku — the same models on the commercial plans, not a limited version.

    What can a nonprofit do with Claude?

    Common uses include grant writing, donor stewardship, program evaluation, and board and compliance documentation, plus integrations with Benevity, Blackbaud, and Candid.

    Is there training for nonprofit staff?

    Yes. Anthropic and GivingTuesday offer a free “AI Fluency for Nonprofits” course, and the $150M Claude Corps fellowship provides hands-on implementation support.

    Want to see how discounted seats stack up against standard plans? Use our Claude pricing calculator, or compare tiers in our guide to Claude for business.

  • I Let Claude Run on My Business. The Moment That Mattered Was When It Said No.

    I Let Claude Run on My Business. The Moment That Mattered Was When It Said No.

    For the past week or so I’ve been building a real operation with Claude — not a demo, not a clever prompt, an actual business a partner of mine is about to run.

    It built the storefront: a full ladder of products, from a $7 scorecard up to a complete operating system, each one wired to checkout and set to deliver itself the second someone buys. It built a redemption engine, so my partner can give out a code from a stage and the right person instantly gets the product while we capture the lead. It drafted a productized lead-generation offer — the pricing, a one-page pitch, even a scorecard to decide which contractors are a fit. When the server’s email quietly broke, it traced the real cause — a file permission, three layers down — and fixed it.

    That’s the part everyone wants to talk about: look what it can do. And it’s real. But it’s not what I’ll remember from this week.

    The moment that mattered

    I asked Claude to check whether a call-tracking number was set up correctly on the site. It looked, confirmed the number was live and routing to the right phone — and then, because it’s thorough, started to clean up a small labeling gap on that number.

    And then it stopped itself.

    A safety layer caught the action before it ran and refused it. The reason it gave was almost uncomfortably precise: you asked me to verify this, not to change it. This is a live system other people depend on. That’s your call, not mine.

    I’d only asked it to look. It had drifted toward changing a shared, live system — exactly the kind of small, well-meant overstep that’s easy to miss — and something stopped it and handed the decision back to me.

    I’d spent a week watching this thing demonstrate real capability. The moment it earned my trust was the moment it demonstrated restraint.

    Capability was never the scary part

    That’s backwards from how most people are sizing up AI right now. The whole conversation is capability — what can it do, how much, how fast. But if you’re actually putting this into your business, capability was never the scary part. The scary part is an eager, capable system taking a consequential, hard-to-undo action on something live because it technically could, and because you weren’t specific enough.

    What protected me wasn’t that the AI was timid by personality. It’s that the whole thing is built so the more consequential, irreversible, and shared an action is, the more a human has to be in the loop. Reading something? Go ahead. Changing a live system someone else relies on, when that wasn’t clearly asked for? Stop and ask. The gate tightens exactly as the stakes rise.

    And the part that actually sold me: when I asked how that worked, it explained its own guardrails plainly. It didn’t pretend it had no limits, and it didn’t pretend it could talk its way around them. It told me where the brakes are, who controls them (me), and what it genuinely can’t see about its own safety layer. An AI that’s honest about what it won’t do is a lot easier to trust with what it will.

    What I’d take from it

    If you’re bringing AI into your operation, here’s what I’d take from my week: don’t just ask what it can do. Ask what it does when it isn’t sure. Ask what happens at the edge — the live system, the irreversible change, the thing you didn’t quite specify. That answer matters more than the length of the feature list, because that’s the moment that either protects your business or burns it.

    The most capable AI in the room is impressive. The one that knows what it shouldn’t do without you is the one you can actually build on. I got to see both this week. Turns out they were the same one.

  • Claude Tag Pricing: Enterprise vs Team, and When Self-Hosting Wins

    Claude Tag Pricing: Enterprise vs Team, and When Self-Hosting Wins

    This is part of our Claude Tag field guide for agencies. Start with the overview: Claude Tag: A Builder’s Guide for Agencies.

    The first thing to understand about Claude Tag pricing is that Claude Tag doesn’t have a price. There’s no separate line item, no per-feature fee. It’s included with the plans it runs on — Claude Team and Claude Enterprise, in beta — so the real question isn’t “what does Claude Tag cost,” it’s “which plan are you on, and is per-seat the right model for how you work.”

    What you’re actually paying for

    Claude Tag is a capability of two existing plans, not a product you buy on its own:

    • Claude Team is straightforward per-seat: a flat monthly price per user (premium seats cost more for higher usage). Predictable, easy to budget, good for a defined internal team.
    • Claude Enterprise is seat-plus-usage: a per-seat fee, and then the tokens your team consumes — in chat, Claude Code, or Cowork — billed on top. It adds controls like role-based access, but the total depends on how heavily you use it.

    Because the two plans bill on different logic, the “cheaper” one depends entirely on your usage shape. We dig into the Enterprise side in detail in Claude Enterprise Pricing: What Large Organizations Pay.

    The launch credit (worth knowing now)

    At launch, Anthropic is subsidizing early adoption: as of June 2026, it’s offering $1,000 in Claude Code and Cowork credits for every Enterprise seat activated by July 2, 2026. For a team that was going to adopt anyway, that credit covers a meaningful chunk of early usage — it makes the “turn it on internally and try it” decision close to free. It’s time-boxed, so if Enterprise is on your radar, the math is best before that date.

    When paying per seat is the right call

    For a single internal team, the per-seat model is the obvious answer. You get a current-generation teammate (Claude Tag runs on Opus 4.8) with no infrastructure to build, the launch credit softens the ramp, and ambient mode is safe to use because all the data is yours. Buy the seats and move on.

    When building your own loop wins

    Per-seat pricing is built for one company’s team. It is not built for an agency running many clients through one operation — and that’s where the calculus flips. Building your own gated Slack–to–AI loop starts to beat paying per seat when:

    • You need hard isolation between clients that per-seat access controls don’t give you. Isolation has to be architectural, not a setting — see The Multi-Client Isolation Trap.
    • You want to own the credential and the model path, so no client’s API key or context lives where it could leak.
    • The approval gate is the product — you need a human signing off on every outbound deliverable, wired into the architecture, not bolted on.
    • Seat counts get large or spiky, where a usage-based loop you control can undercut a per-seat bill.

    We didn’t reason our way to this in a spreadsheet — we built that loop before Claude Tag launched, for exactly these reasons. The story is in We Built a Slack AI Teammate Before Claude Tag.

    The honest answer

    For your internal team, adopt Claude Tag on a Team or Enterprise plan and take the launch credit — it’s the cheapest path to a real AI teammate. For multi-client delivery, the per-seat model isn’t the whole answer, because the thing you’re really buying — isolation, control, and a human in the loop — is exactly what you have to build yourself. That’s the part we build for clients at Tygart Media. Start at the pillar: Claude Tag: A Builder’s Guide for Agencies.

  • How to Set Up Claude Tag in Slack (and What to Lock Down First)

    How to Set Up Claude Tag in Slack (and What to Lock Down First)

    This is part of our Claude Tag field guide for agencies. Start with the overview: Claude Tag: A Builder’s Guide for Agencies.

    Setting up Claude Tag in Slack takes a few minutes. The clicks are easy. The decisions you make while you click — who can reach it, which channels it sees, whether it’s proactive — are the part that actually matters. This is a security-first walkthrough: how to install it, and what to lock down before you do.

    The install, in plain steps

    1. Open the Install Claude for Slack link, which takes you to the Slack Marketplace listing.
    2. Click Add to Slack and approve the requested permissions.
    3. Choose the scope: the whole workspace (Anthropic’s recommended default) or a specific set of channels.

    One important gotcha: only a Slack Primary Owner or Owner can set up Claude Tag’s access and channels. The Admin role can’t do this part. If you’re rolling it out for a team, make sure an Owner is the one configuring access — otherwise you’ll get halfway and stall.

    Lock this down first: who can reach Claude

    Claude Tag gives you three Member Access modes. Pick the tightest one that still lets the right people work:

    • Anyone in the Slack workspace — broadest; fine for a single internal team, risky if outside collaborators or clients are guests in your workspace.
    • Any member of your Claude organization — narrower; ties access to your Claude org, not just Slack presence.
    • Role-based access — tightest; only members whose role allows it. This one is available on the Claude Enterprise plan.

    Default to the narrowest mode that doesn’t block real work. You can always widen later; clawing access back after the fact is harder.

    Then decide what Claude can see

    Access is who can talk to Claude. Visibility is what Claude can read — and it’s the bigger lever. Two settings deserve a deliberate decision, not a default:

    • Cross-channel learning is permission-gated — Claude only learns from other channels and data sources you allow, and it doesn’t report from private channels. Grant it per channel, and never let a channel holding one client’s (or one regulated dataset’s) data feed learning that other work can draw on.
    • Ambient mode turns Claude proactive. Leave it off for anything client-facing or sensitive, and on only where all the data is yours. We break down that call in Claude Tag Ambient Mode: Useful Teammate or Context-Bleed Risk?

    The lock-down-first checklist

    1. Map channels to trust boundaries before you enable anything — mark each channel internal, client, or regulated.
    2. Set Member Access to the narrowest mode that works.
    3. Ambient mode OFF by default; on only for internal-only channels.
    4. Cross-channel learning granted per channel, never from client/regulated channels.
    5. Isolate client work in its own space, not just a channel in one shared brain — the reasoning is in The Multi-Client Isolation Trap.
    6. Keep a human on the ship button for anything that leaves the building.

    If you’re migrating from the old app

    Claude Tag replaces the legacy Claude in Slack app. The old app switches over on August 3, 2026, and administrators have a 30-day window to opt in and control channel-level access. Don’t treat the migration as a silent upgrade — it’s the moment to redo these access and visibility decisions from scratch. More on what changed: Claude Tag vs. the Old Claude in Slack App.

    For the exact, current setup screens, Anthropic keeps an admin setup guide in its documentation; the decisions above are what to bring to it. For the full field guide, start at the pillar: Claude Tag: A Builder’s Guide for Agencies.

  • Claude Tag Ambient Mode: Useful Teammate or Context-Bleed Risk?

    Claude Tag Ambient Mode: Useful Teammate or Context-Bleed Risk?

    This is part of our Claude Tag field guide for agencies. Start with the overview: Claude Tag: A Builder’s Guide for Agencies.

    Ambient mode is Claude Tag’s headline feature and its single most consequential setting. Turn it on and Claude stops waiting to be asked — it starts watching the channels it’s in and speaking up when it thinks you’d want to know something. Whether you should enable it isn’t a yes-or-no question. It’s a where question, and getting the where right is the whole game.

    What ambient mode actually does

    By default, Claude Tag is reactive: you @-mention it, it works, it replies. With ambient behavior enabled, it becomes proactive. Anthropic describes it as Claude keeping you updated about whatever it thinks you might need to know — flagging relevant information from across the channels it’s in and the tools it’s connected to, and following up on threads or tasks that have gone quiet.

    In practice that means three things: it surfaces context you didn’t ask for, it connects information across more than one channel, and it chases loose ends nobody assigned it. Those are exactly the behaviors that make it feel like a teammate instead of a tool.

    Where it’s a superpower

    Inside a single team, ambient mode is close to magic. Every channel belongs to the same company, so “learning across channels” only ever connects your own dots. A proactive teammate that remembers the forgotten follow-up, links the spec to the standup, and flags the blocker before it bites is pure upside. This is the version Anthropic runs internally, and it’s why they can say a large share of their product team’s code now comes from their own version of the tool.

    If your Slack workspace is one company’s data and one team’s work, turn ambient mode on and enjoy it.

    Where it’s a risk

    Ambient mode’s proactive, cross-channel nature is exactly what makes it dangerous in two situations:

    • Multiple clients in one operation. The moment a proactive teammate is “surfacing relevant information from across channels,” relevance becomes the judge of what crosses the line between Client A and Client B. That’s a context-bleed risk we’ve lived — the whole subject of The Multi-Client Isolation Trap.
    • Regulated or sensitive data. Anywhere an unprompted message pulling context from elsewhere could expose something it shouldn’t — health, financial, legal, HR — proactive surfacing is a liability, not a convenience.

    A simple decision framework

    Don’t decide ambient mode globally. Decide it per surface, with one question: is everything this Claude can see owned by the same trust boundary?

    Surface Ambient mode Why
    Internal team channels (one company) ON Cross-channel proactivity only connects your own data
    Client-facing / multi-tenant channels OFF Proactive surfacing is where one client’s context leaks into another’s
    Regulated / sensitive-data channels OFF Unprompted context-pulling is a compliance liability

    The rule of thumb: ambient mode should be on where the data is all yours, and off everywhere a human should still be pulling, not the AI pushing.

    If you do turn it on

    Enable it deliberately, not by default. Map which channels hold which trust boundary before you flip the switch, keep client and regulated channels out of cross-channel learning, and audit what the assistant can actually see. That sequencing — boundaries first, then ambient — is exactly how we walk through it in How to Set Up Claude Tag in Slack.

    The bottom line

    Ambient mode isn’t good or bad — it’s powerful, and power needs a boundary. For internal teams, it’s the best part of Claude Tag. For client work, it’s the part to leave off until isolation is airtight. For the full picture, start at the pillar: Claude Tag: A Builder’s Guide for Agencies.

  • Claude Tag: A Builder’s Guide for Agencies (From a Team That Shipped It First)

    Claude Tag: A Builder’s Guide for Agencies (From a Team That Shipped It First)

    Today Anthropic launched Claude Tag — a new way to work with Claude that starts inside Slack. Instead of a chatbot you visit, Claude joins your workspace as a teammate. You @-mention it with a request, it breaks the task into stages, works through them, and replies in the thread with what it made.

    We read the announcement with a strange feeling, because we’d been running a version of this loop for client delivery for weeks. So this isn’t a reaction piece written from the outside. It’s a field guide from a team that built the same thing first — what Anthropic got right, what’s genuinely better in their version, and the one design choice that’s quietly dangerous if you run an agency.

    What Claude Tag actually is

    • A Slack-native teammate you delegate to by tagging @Claude — no separate app to open.
    • Multiplayer by default: one shared Claude per channel; anyone can see its work and pick up where the last person left off.
    • Context that compounds: it follows the channel over time, and with permission can learn from other channels and data sources.
    • Ambient mode: turn it on and Claude takes initiative — surfacing what’s relevant, flagging stale threads, following up on forgotten tasks.

    It runs on Opus 4.8, replaces the older “Claude in Slack” app (admins opt in within 30 days), and is in beta for Enterprise and Team plans. Anthropic says 65% of their product team’s code now comes from their internal version. That number is the tell: this isn’t a toy.

    What they got right

    1. The unit of work is a request, not a conversation. “@Claude, draft the launch email and three follow-ups” is how people actually delegate.
    2. Shared context beats private chats — auditable and collaborative; private AI sessions create shadow work nobody can review.
    3. It meets people where the work already is. The work happens in Slack, so the AI lives in Slack.

    The one thing agencies have to get right (and Claude Tag doesn’t, by default)

    Claude Tag’s standout features — ambient mode and cross-channel learning — are wonderful when every channel belongs to one company. But an agency is many clients sharing one operation. The moment your AI teammate “learns across channels and data sources,” context from Client A can surface in work for Client B.

    We learned this by living it. In an early pilot, a single shared context produced client deliverables that pulled in details from the wrong account. Nothing left the building, but the signal was clear: for client work, ambient cross-channel learning is not a feature — it’s a breach waiting for a deadline.

    So we rebuilt around two non-negotiables:

    • Hard isolation per client — each client’s room is walled, enforced in the architecture, not a prompt you hope it obeys.
    • Approve-before-ship — the AI drafts; a human reviews; only then does it go out.

    If you take one thing from this guide: the two things that make Claude Tag magical inside a company are the two things you must switch off — or wall off — to use it safely for clients.

    The pattern that works: split by surface

    Surface Use Why
    Your internal team Adopt Claude Tag Ambient cross-channel learning is a feature when all the data is yours
    Client-facing delivery Isolated room + approval gate Isolation and human sign-off are the product

    How to roll it out without getting burned

    1. Map channels by trust boundary; client-data channels don’t get cross-channel learning.
    2. Default ambient mode OFF for anything client-facing.
    3. Keep humans on the ship button for anything that leaves the building.
    4. Audit what the AI can see — your permission is the control; set it deliberately.
    5. Separate client work into isolated spaces, not just channels in one shared brain.

    Where this goes

    Claude Tag is a milestone: the AI teammate is now an operating model, not a demo. For internal teams, adopt it. For client work, the hard, valuable part — isolation, trust, a human in the loop — is still yours to own. That’s what we build for clients at Tygart Media.

    The rest of the field guide

    This pillar is the overview. The cluster goes deeper:

  • Claude Tag vs. the Old Claude in Slack App: What Changed

    Claude Tag vs. the Old Claude in Slack App: What Changed

    This is part of our Claude Tag field guide for agencies. Start with the overview: Claude Tag: A Builder’s Guide for Agencies.

    If your team already used the “Claude in Slack” app, Claude Tag is not an add-on — it’s the replacement. Anthropic has said Claude Tag replaces the existing Claude in Slack app, administrators have a 30-day window to opt in, and the legacy app is retired on August 3. So this isn’t a “should we try it” decision. It’s a migration with a clock on it. Here’s what actually changed, and what to check before you flip the switch.

    What’s genuinely new

    The old integration was, in practice, a way to summon Claude in a thread. Claude Tag changes the model from “a chatbot you call” to “a teammate that stays.” Four things are new:

    • Multiplayer per channel. Within a given Slack channel, there’s one Claude that interacts with everyone. Anyone can tag it in and pick up where the last person left off, instead of each person holding a private session.
    • Ambient mode. When enabled, Claude proactively keeps people updated about what it thinks they need to know — flagging relevant information, following up on forgotten threads — rather than waiting to be asked.
    • Cross-channel learning. With permission, Claude can learn from other Slack channels and data sources. (Anthropic notes it doesn’t report from private channels.)
    • Opus 4.8 underneath. Claude Tag runs on Opus 4.8, so the reasoning behind the delegation is the current-generation model, not whatever the old app was pinned to.

    The migration timeline, plainly

    Three dates and facts matter:

    1. Claude Tag is available today in beta for Claude Enterprise and Team customers.
    2. Administrators have 30 days to opt in and migrate.
    3. The old Claude in Slack app is retired on August 3. If you do nothing, that capability goes away.

    Anthropic is also issuing an introductory launch credit to eligible Enterprise and Team organizations, which makes the trial period genuinely low-stakes for internal use.

    What to check before you switch — especially if you serve clients

    For a single-company team, migrating is close to a no-brainer: you get a better model and a more capable teammate, and the launch credit covers the experiment. If you’re an agency or anyone handling more than one client’s data in one workspace, three checks come first:

    1. Decide cross-channel learning per channel, not globally. The new superpower is also the new risk. A channel that holds one client’s data should never feed learning that another client’s work can draw on. Map your channels to trust boundaries before you grant any cross-channel permission.
    2. Default ambient mode OFF for client-facing channels. Proactive surfacing is wonderful internally and dangerous across tenants. Turn it on where the data is all yours; leave it off where it isn’t.
    3. Keep your approval gate. Whatever human sign-off you had on outbound work in the old setup, carry it forward. A more autonomous teammate raises the stakes on “who hits send.”

    Our take

    Adopt it internally now — the model upgrade and the multiplayer surface are worth it, and the clock makes the decision for you anyway. For client delivery, migrate deliberately: the same features that make Claude Tag better make isolation harder, and isolation is the thing you can’t get wrong. We unpack exactly that failure mode in The Multi-Client Isolation Trap, and the on/off call for proactive behavior in Claude Tag Ambient Mode.

    For the full picture, start at the pillar: Claude Tag: A Builder’s Guide for Agencies.

  • We Built a Slack AI Teammate Before Claude Tag

    We Built a Slack AI Teammate Before Claude Tag

    This is part of our Claude Tag field guide for agencies. Start with the overview: Claude Tag: A Builder’s Guide for Agencies.

    The night before Anthropic launched Claude Tag, we shipped two client deliverables through a Slack-based AI teammate we had built ourselves. We weren’t racing anyone and we had no idea an announcement was coming the next morning. We were just doing the work the way we’d been doing it for weeks: post a request in a channel, let Claude draft, approve it, and let it go out.

    So when Anthropic described Claude Tag — tag @Claude with a request, and it breaks the task into stages and works through them in the thread — we recognized it on sight. This is the build log of the version we made first: what it is, why we put it in Slack, and the one piece we deliberately kept under human control.

    Why we were building an AI teammate in Slack at all

    We didn’t set out to build an “AI tool.” We set out to close the gap between a decision and the thing the decision produces. A lead comes in and someone says “we should send the follow-up sequence today.” A week ends and someone says “the client update needs to go out.” The decision is made in seconds; the production used to take an hour. That hour is where work stalls.

    Slack was the obvious surface because that is where the deciding already happens. We didn’t want a separate dashboard nobody opens, or a chatbot in another tab that creates a second copy of the conversation. We wanted the request and the result to live in the same thread, where anyone on the team can see both. Putting the AI where the work already is turned out to be most of the design.

    The loop, stage by stage

    The whole system is one loop with four moves:

    1. Request. Someone posts a plain-language ask in a channel — “draft the new-lead follow-up sequence,” “write this week’s update post.” No special syntax, no form.
    2. Draft. The teammate picks it up, breaks it into stages, and produces the actual deliverable in the thread — not a summary of what it would do, the thing itself.
    3. Claim and approve. A human takes the draft, reads it, edits if needed, and signs off. Nothing moves on the AI’s say-so alone.
    4. Ship. On approval, the deliverable goes to its real destination — the CRM, the CMS, the inbox — and the thread records that it happened.

    The night we ran it end to end, twice, the part that struck us wasn’t the drafting. It was how natural the “claim and approve” step felt. Delegating to the teammate looked exactly like delegating to a person: ask in the channel, get a draft back, give it a yes.

    The runner that holds no keys

    The piece we’re proudest of is invisible in the thread. The process that reads the queue and carries out approved work does not carry standing credentials. The keys to the CRM, the publishing platform, the email system — none of them live inside the bot. They sit in the platform’s secret store and are handed to the action at the moment it runs, scoped to that job.

    This sounds like plumbing, but for an agency it is the difference between safe and reckless. The component most exposed to the outside world — the thing listening to a chat channel — is the component holding the least. If that surface were ever compromised, there is no client’s API key sitting in it to steal. We built it that way before it was convenient, because client trust is the entire business.

    What surprised us

    • A request is a better unit than a conversation. “Draft the launch email and three follow-ups” is how people actually delegate. Framing the work as a request instead of a chat changed how the team used it — less hand-holding, more handing-off.
    • Visible beats private. Because the work happened in a shared channel, anyone could see what was asked and what came back. Private AI sessions create shadow work nobody can review. Doing it in the open made it auditable by default.
    • The approval step wasn’t a bottleneck. It was the product. We expected the human sign-off to feel like friction. Instead it was the thing that let us trust the output enough to send it to a client at all.

    What Claude Tag changes for us

    Anthropic just productized the surface we’d been hand-building: a Slack-native teammate, multiplayer per channel, with an ambient mode and cross-channel learning, running on Opus 4.8. For our internal team, that’s a gift — we can adopt it and retire some of our own scaffolding.

    For client delivery, the hard and valuable part is still ours to own: keeping each client’s context walled off from every other, and keeping a human on the ship button. Those two things are exactly what Claude Tag’s best features work against by default — which is the whole subject of the next piece: Claude Tag for Agencies: The Multi-Client Isolation Trap. For the full picture, go back to the pillar: Claude Tag: A Builder’s Guide for Agencies.

  • Claude Fable 5 Pricing and Access (2026)

    Claude Fable 5 Pricing and Access (2026)

    Last verified: June 13, 2026

    Claude Fable 5 (claude-fable-5) is Anthropic’s most capable widely released model, built for the most demanding reasoning and long-horizon agentic work. On the Claude API it is priced at $10 per million input tokens and $50 per million output tokens — double the rate of Claude Opus 4.8 — with a 1M-token context window and up to 128K output tokens per request. It reached general availability on June 9, 2026. The verified pricing and access details are below.

    Pricing at a glance

    All figures below are from Anthropic’s official pricing and models pages. Prices are in USD per million tokens (MTok). Fable 5 includes the full 1M-token context window at standard pricing — there is no long-context premium.

    Item Claude Fable 5
    Model ID (API) claude-fable-5
    Base input $10 / MTok
    Output $50 / MTok
    5-minute cache write $12.50 / MTok
    1-hour cache write $20 / MTok
    Cache hit / read $1 / MTok
    Batch API input / output $5 / MTok · $25 / MTok
    Context window 1M tokens
    Max output 128K tokens

    How Fable 5 compares to Opus, Sonnet, and Haiku

    Fable 5 sits at the top of Anthropic’s lineup, a tier above the Opus models. The per-token cost difference is the clearest way to see where it fits.

    Model Input $/MTok Output $/MTok Context Max output
    Claude Fable 5 $10 $50 1M 128K
    Claude Opus 4.8 $5 $25 1M 128K
    Claude Sonnet 4.6 $3 $15 1M 64K
    Claude Haiku 4.5 $1 $5 200K 64K

    Where you can use Fable 5

    At general availability, Fable 5 is offered across Anthropic’s first-party API and all major cloud platforms, plus claude.ai subscription plans (subject to the access note below). The model IDs differ by platform.

    Surface Availability / model ID
    Claude API (first-party) Generally available — claude-fable-5
    Claude Platform on AWS Generally available — claude-fable-5
    Amazon Bedrock Generally available — anthropic.claude-fable-5
    Google Vertex AI Generally available — claude-fable-5
    Microsoft Foundry Generally available
    claude.ai — Pro, Max, Team, Enterprise Promotional access June 9–22, 2026 (see below)
    claude.ai — Free plan Not included

    Consumer-plan access and the promotional window

    For claude.ai subscribers, Anthropic launched Fable 5 with a time-limited promotion rather than a permanent plan inclusion. From June 9 through June 22, 2026, Fable 5 was included on the Pro, Max, Team, and seat-based Enterprise plans at no extra charge. During that window, Anthropic’s documentation states that Fable 5 usage “counts toward your plan’s usage limits, and you won’t be charged anything extra,” but that it draws from those limits “at a higher rate than other models.” The Free plan was explicitly excluded.

    Anthropic’s announced plan was that after June 22, 2026, Fable 5 would no longer be included in plan usage limits, and continued use on claude.ai would require usage credits — a pay-as-you-go balance for usage beyond what a plan includes.

    Integration notes that affect cost and handling

    Fable 5 differs from the Opus, Sonnet, and Haiku models in a few ways that matter when you wire it into an application. It ships with safety classifiers that can decline a request: when that happens, the Messages API returns stop_reason: "refusal" as a successful HTTP 200 response, not an error. You are not billed for a request that is refused before any output is generated, and Anthropic provides server-side, client-side, and manual fallback paths to retry on another Claude model. Adaptive thinking is always on (thinking: {"type": "disabled"} is not supported), and the raw chain of thought is never returned — thinking.display controls whether thinking blocks contain a summary or are empty. Fable 5 also uses the tokenizer introduced with Opus 4.7, which can produce roughly 30–35% more tokens for the same text than older models, so re-baseline your token counts rather than assuming parity with earlier Claude models.

    How much does Claude Fable 5 cost?

    On the Claude API, Fable 5 costs $10 per million input tokens and $50 per million output tokens. Prompt-cache writes are $12.50/MTok (5-minute) or $20/MTok (1-hour), cache reads are $1/MTok, and the Batch API halves the rate to $5/MTok input and $25/MTok output.

    Is Fable 5 more expensive than Claude Opus 4.8?

    Yes. Fable 5 is priced at exactly double Opus 4.8 on both input ($10 vs $5 per MTok) and output ($50 vs $25 per MTok). Both share a 1M-token context window and 128K max output.

    Which claude.ai plans include Fable 5?

    From June 9 to June 22, 2026, Fable 5 was included on the Pro, Max, Team, and seat-based Enterprise plans at no extra cost, drawing from plan usage limits at a higher rate. The Free plan was not included. Anthropic’s plan was to move continued claude.ai use to usage credits after June 22.

    What is the difference between Fable 5 and Mythos 5?

    They share the same specs ($10/$50 per MTok, 1M context, 128K output) and June 9, 2026 launch date. Fable 5 is the generally available model with built-in safety classifiers that can decline requests; Mythos 5 is offered only in limited availability.


  • Claude Message Batches API: 50% Pricing, Limits and How It Works (2026)

    Claude Message Batches API: 50% Pricing, Limits and How It Works (2026)

    Last verified: June 13, 2026

    The Message Batches API lets you submit up to 100,000 Claude requests in a single call and receive results asynchronously — at exactly 50% of standard token prices. Most batches finish in under an hour. Results remain downloadable for 29 days. This page covers every verified limit, the per-tier rate limit tables, and how batch pricing stacks with prompt caching.

    Pricing: 50% off standard rates

    Every token processed through the Message Batches API is billed at half the standard input and output price. No quality difference from synchronous requests — only timing. The table below shows verified batch prices for active models.

    Model Batch input (per MTok) Batch output (per MTok) Standard input (per MTok) Standard output (per MTok)
    Claude Fable 5 $5.00 $25.00 $10.00 $50.00
    Claude Opus 4.8 $2.50 $12.50 $5.00 $25.00
    Claude Opus 4.7 $2.50 $12.50 $5.00 $25.00
    Claude Opus 4.6 $2.50 $12.50 $5.00 $25.00
    Claude Opus 4.5 $2.50 $12.50 $5.00 $25.00
    Claude Sonnet 4.6 $1.50 $7.50 $3.00 $15.00
    Claude Sonnet 4.5 $1.50 $7.50 $3.00 $15.00
    Claude Haiku 4.5 $0.50 $2.50 $1.00 $5.00

    Source: platform.claude.com/docs/en/build-with-claude/batch-processing

    Key limits at a glance

    Limit Value
    Maximum requests per batch 100,000
    Maximum batch payload size 256 MB
    Typical completion time Under 1 hour
    Hard expiration window 24 hours from creation
    Result retention period 29 days after creation
    Zero Data Retention eligible No
    Results format JSONL, streamed via results_url
    Supported models All active Claude models

    A batch expires if processing has not completed within 24 hours. Any individual request within that batch that did not finish is marked expired — you are not billed for expired or errored requests. Batch results (the JSONL file) are accessible for download for 29 days after the batch was created; after that the batch object itself is still visible but results can no longer be downloaded.

    Message Batches API rate limits by tier

    The Message Batches API has its own rate-limit pool, shared across all models, separate from the standard Messages API limits. The “processing queue” count refers to individual batch requests (not batches) that have been submitted but not yet completed by the model.

    Tier RPM (API calls) Max batch requests in processing queue Max batch requests per batch
    Tier 1 50 100,000 100,000
    Tier 2 1,000 200,000 100,000
    Tier 3 2,000 300,000 100,000
    Tier 4 4,000 500,000 100,000

    Source: platform.claude.com/docs/en/api/rate-limits

    RPM here limits how fast you can make HTTP requests to the Batches API endpoints (create, retrieve, list, cancel). It does not limit how many individual requests inside a batch are processed per minute — that is governed by the queue cap above. If high demand causes processing to slow, more individual requests within a batch may reach the 24-hour expiration limit.

    Stacking batch pricing with prompt caching

    The Batches API documentation explicitly states that the 50% batch discount and prompt caching discounts stack. Cache writes incur a one-time cost at 1.25x the base input rate (5-minute TTL) or 2x (1-hour TTL); subsequent cache reads cost 0.1x the base input rate. Because batches process asynchronously and may take longer than 5 minutes, Anthropic recommends using the 1-hour cache duration for batch requests that share large context.

    The following example uses Claude Opus 4.8 (standard input: $5.00/MTok) to show what each token type costs in a batch with a 1-hour cached system prompt.

    Token type Multiplier applied Effective price per MTok How calculated
    Uncached input (standard) 1x $5.00 Baseline
    Uncached input (batch) 0.5x $2.50 50% batch discount
    Cache write — 1h TTL (batch) 2x × 0.5x = 1x $5.00 2x write cost, then 50% batch
    Cache read (batch) 0.1x × 0.5x = 0.05x $0.25 10% read cost, then 50% batch
    Output (batch) 0.5x of $25.00 $12.50 50% batch discount on output

    In practice: if you cache a 50,000-token system prompt once and then read it across 1,000 batch requests, the cache write costs $0.25 (50K tokens at $5.00/MTok effective), while 1,000 cache reads cost $12.50 total (50M tokens at $0.25/MTok). The same 50 million tokens without caching would cost $125 in batch input (50 MTok at the $2.50/MTok batch rate). Cache hit rates on batches vary; Anthropic’s documentation notes typical rates of 30% to 98% depending on traffic patterns, since batch requests are processed concurrently rather than sequentially.

    How results come back

    When the batch finishes (or the 24-hour limit is reached), a results_url property is set on the batch object. Results are in JSONL format — one JSON object per line, in any order (not necessarily matching submission order). Each result carries the custom_id you assigned, plus a result object of type succeeded, errored, canceled, or expired. Streaming the results file rather than downloading it all at once is recommended for large batches. You are not billed for errored, canceled, or expired requests.

    Does the Batches API count against my standard Messages API rate limits?

    No. The Message Batches API has its own rate-limit pool that is tracked separately from the standard Messages API RPM, ITPM, and OTPM limits. You can use both simultaneously up to their respective limits.

    What happens if my batch does not finish within 24 hours?

    Any individual requests within the batch that did not complete are marked expired. You are not billed for those requests. The batch itself moves to ended status and whatever results did complete are available at the results_url.

    Can I use extended thinking, tool use, or vision in a batch?

    Yes. The Batches API supports vision, tool use (including server tools such as web search and code execution), system messages, multi-turn conversations, and extended thinking. The parameters not supported are stream: true, fast mode (speed), Threads parameters, and max_tokens: 0.

    How long are batch results available for download?

    Results are available for 29 days after the batch was created. After that window, the batch object remains visible in the Console and via the API, but the results file can no longer be downloaded.

    Is the Batches API eligible for Zero Data Retention?

    No. The Message Batches API is explicitly excluded from Zero Data Retention (ZDR). Data is retained under the feature’s standard retention policy regardless of your organization’s ZDR settings.