LunaDocs

Loading search...

PortuguêsSign in to the console
On this page

Meta costs

Use with AI

Luna charges only for the number capacity of the plan. WhatsApp usage is charged by Meta, directly to the business that owns the number. This guide summarizes the Meta charging rules in force and what they change for whoever integrates.

Who charges for what#

Luna charges only for the capacity of connected numbers in the plan. It never charges by the message sent or received, and no API limit varies with the plan.

The technical limits the API applies (requests per minute, webhook endpoints, connection link validity, file size, sends per second) come from GET /v1/limits, each with key, label, value, unit and reason. They are the same for every customer and exist for capacity or because Meta imposes them. It asks for numbers:read.

Meta charges for WhatsApp usage directly to the business that owns the number, on the payment method registered in that business’s WhatsApp account at Meta. That is why each business needs its own Meta account, with its own payment method. Luna does not intermediate, advance or pass on that payment.

What Meta charges since October 1, 2026#

The rules below were read on Meta’s pricing page on October 7, 2026. The amounts are not here: they vary by message category and by the recipient’s country, and Meta updates them on the first day of each quarter. Meta’s rate card is the reference.

Whoever needs to show these rules inside their own product reads GET /v1/meta-pricing: the rules list (each rule with key, title and text), the day Luna read them in readAt, and the addresses of the rate card (sourceUrl) and of the AI Providers policy (aiProvidersUrl). It carries no monetary values. It asks for numbers:read.

  • Replies inside the 24-hour window, which Meta calls service messages: each number has 1,000 free service messages a month, and the balance does not roll over. From the 1,001st on, Meta charges each delivered message. The month turns at midnight, in the messaging account’s time zone.
  • A utility template inside an open window is no longer free. Meta now charges it even with the 24-hour window open.
  • A marketing template is always charged, inside or outside the window.
  • A conversation started from a click-to-WhatsApp ad: replying inside the service window opens a free period of up to 7 days, for marketing, utility, authentication and service.
  • Authentication and utility have volume tiers: the rate of the next tier is lower. Meta does the counting, across the whole business portfolio, and it restarts every month.

For whoever integrates, the practical consequence is to plan the first send and high-volume replies with the payment method already registered. The 24-hour window still decides whether a free-form message can go out: see Send messages.

General-purpose AI assistants#

Meta calls general-purpose AI assistants AI Providers, and treats them under a policy of its own. The service-message rule above does not apply to them. Read Meta’s policy for AI Providers before deciding whether your product falls under it.

When Meta classifies a sent message under that charge, its pricing.category arrives as general_purpose_ai, in GET /v1/messages/{id}, in GET /v1/messages and in the message.status event, and the console shows the label "General-purpose AI". It is the AI Provider charge, which Meta makes to the business that owns the account, per service message, and it applies to Brazil. Luna only displays the classification: it does not add it up, does not convert it into an amount and charges nothing on it. A business’s support agent, answering about the business’s own service, pays as an ordinary service message; the general_purpose_ai category shows up when the main product is a general-purpose assistant.

How to check what Meta charged#

Luna returns the cost classification Meta applied to each sent message, with Meta’s names, and does not return a price. The pricing object comes in GET /v1/messages/{id} and in the message.status event, with billable, pricing_model, type and category. Meta reports it only on sent and on one of delivered and read: until it does, the field is null. Meta is going to discontinue billable, so read type and category together. The values are Meta’s and can gain new ones: do not treat them as a closed list.

What Luna returns is what helps predict the category. The template’s category comes in the category field of GET /v1/templates. The state of each contact’s service window comes in GET /v1/conversations, in the windowOpen, windowExpiresAt and windowSource fields. Both are in the API reference.

To see the usage Meta measures for a number in the period, use GET /v1/usage?numberId=. Luna reads Meta’s pricing_analytics with the business’s token and passes the points through as Meta reports them: pricing category and type, the tier, the country, the volume and the approximate cost, in the currency of the business’s account at Meta. Each point comes from a single number and carries numberId, phoneNumberId and currency, the currency of its account; the response has no total, and notice carries the warning that the value is an approximation and that Meta charges the business directly. Each read spends one unit of Meta’s management limit, so the read of each number is kept for five minutes (readAt says when the read is from). None of this goes into the Luna subscription.

To pass usage on to one of your customers, send externalId instead of numberId (exactly one of the two; both, or neither, answer 400 with campos): GET /v1/usage?externalId=cliente-42&start=2026-11-01&end=2026-12-01&granularity=MONTHLY. Luna reads each number of that customer and returns the points of all of them in data, each with its own numberId and currency. A customer with accounts in different currencies gets points in different currencies, and Luna never adds currencies: group by numberId and currency on your side. numbers lists the numbers covered, including the ones that had no point and the ones left out (read: false, with reason: number_disconnected or phone_not_read_yet). granularity is DAILY (the default), MONTHLY or HALF_HOUR, and Meta limits the period of each. With format=csv the response comes as text/csv, one line per point, for your finance team’s spreadsheet; the approximation notice goes in the X-Luna-Notice header. It is still display only: none of this goes into the Luna subscription.

The pricing is for you to display, it is not the invoice. To see what Meta actually charged, check the Billing Hub of the business’s WhatsApp account, and the invoice Meta issues to it. That is where the amount shows up. Luna does not compute money amounts, does not add them up and does not charge on them.