Pax8 Agent

What it can do

• CompaniesYour clients as Pax8 knows them — names, status, location, and billing contacts. The join key behind every client-scoped question here.4skills
  • The client list as Pax8 bills it, filterable by active or inactive status and by where they sit.
  • One company's full Pax8 record, rather than the trimmed list row.
  • Who Pax8 has on file for a client — the people billing and provisioning notices actually reach.
  • A single contact's detail, pulled straight from the client it belongs to.
• Subscriptions & seatsWhat each client is actually buying: product, quantity, billing term, and price — plus the per-subscription change history behind seat drift, and usage detail for consumption-billed products.6skills

  Quantities are seats purchased from Pax8, not seats assigned to users — and nothing here changes a quantity, term, or status.

  • Every active licence and service by client, product, or billing term — the quantity column is the seat count you're paying for.
  • Open one subscription in full — the whole record behind a single line on the bill.
  • How a subscription's quantity and term moved over time — where seat-drift and reconciliation questions get settled.
  • Current charges on a usage-billed subscription, broken out by resource group — the Azure bill before it's a bill.
  • A single usage summary on its own, when you already know which one you want.
  • The individual usage lines under a summary for one specific day — the granular level a spike gets traced at.
• Catalog & pricingEverything Pax8 sells, with partner cost and suggested retail by billing term, the base SKUs a product depends on, and what it asks for at order time.5skills
  • Search the Pax8 catalog by name, vendor, or SKU — what's available to resell and who makes it.
  • One product's full catalog entry, when the list row isn't enough to settle what it actually is.
  • Partner cost and suggested retail by billing term — the cost side of any margin question.
  • Which provisioning fields a product would demand at order time — reference only, since ordering happens in Pax8.
  • The base SKUs a product sits on top of — why an add-on won't stand alone.
• Invoices & spendWhat Pax8 charges you: invoices by status and date range, their line items, the charges already accruing toward the next bill, and the distributor's own finance report over all of it.5skills

  Reads billing records only — it cannot pay, void, dispute, credit, or adjust an invoice or any line on one. These are what the distributor charges you, never what you charge your clients.

  • Your partner invoices by status, date range, or client — paid, unpaid, credited, and what's outstanding.
  • One invoice's header record — totals, dates, and where it stands.
  • The lines that make up an invoice — the revenue side to set against catalog cost when you're checking margin.
  • Charges already building toward the next invoice — the early warning before a surprise arrives.
  • Invoice lines cut and totalled the way Pax8's own finance report does — the whole book by client, product, or period in one pass.
• Orders & quotesHow subscriptions came to exist, and the proposals priced from the catalog — order records and the quote pipeline, both as history you can read.4skills

  Visibility only — it cannot place, amend, or cancel an order, or create, send, or edit a quote. Scheduled and future-dated orders aren't returned by the Pax8 endpoint at all.

  • Orders placed in the Pax8 portal, optionally narrowed to one client — the record of what was bought and when.
  • One order opened out in full — every line on it, as Pax8 recorded it at the time.
  • The quote pipeline by state — draft, sent, accepted, declined, expired — searchable by text.
  • One quote and everything on it, as Pax8 holds it.
• Order fulfilmentWhether the thing you were charged for was ever actually delivered: the queue of orders in flight, what was configured at checkout, the outcome recorded against each one, and every attempt Pax8 made to tell your systems about it.12skills

  Describes delivery into your own fulfilment systems — it cannot retry a delivery, re-send a notification, or change anything about an order.

  • Every order Pax8 is delivering into your own systems, so the queue is one look rather than a client-by-client chase.
  • One delivery opened out in full — the whole record behind a single line in that queue.
  • Only the deliveries that haven't landed yet — the backlog to work, without sifting the whole queue for it.
  • The configuration entered at checkout for an order, version by version — what was asked for, and what changed after.
  • One version of that checkout configuration, when you already know which one is being argued about.
  • The configuration in force for an order right now, without reading its whole version history first.
  • Whether each delivery succeeded or failed, with the outcome Pax8 recorded against it.
  • A single recorded outcome in full, for the order whose delivery is in dispute.
  • Did this order ever finish delivering — the most recent outcome, without walking the whole trail.
  • Every time Pax8 tried to notify your systems about an order — the trail behind a delivery that never arrived.
  • One notification attempt on its own, with what was sent and what came back.
  • The most recent attempt for an order — where to start when a client says their licence never appeared.
• Event deliveryThe live feeds Pax8 pushes into your own systems: what you have subscribed to, what else you could subscribe to, and the delivery trail behind a notification that never showed up.5skills

  Reads the configuration and the delivery log — it cannot create, change, disable, test, or retry a feed.

  • Which event feeds you have pointed at your own systems, and whether each one is still live.
  • One feed's configuration in full — where it sends, what it listens for, and how it has been behaving.
  • Everything Pax8 can notify you about, so you can see what you aren't yet listening for.
  • The delivery trail for one feed — the answer to why a notification never arrived.
  • A single delivery opened out, when you need to see exactly what was sent and what came back.

How it has been taught to work it

Playbooks are the vetted techniques a session loads for this platform — what to check, in what order, and what a number means before it is reported.

• Pax8 ↔ Microsoft 365 — seats bought vs seats owned vs seats assignedAre we paying Pax8 for more Microsoft seats than are assigned — license reconciliation, seat drift, unused/shelfware licenses, billing vs deployment, for one client or across clients.
  Vetted Aug 31, 2026
• Pax8 billing and spend — invoices, run-rate, cost per clientWhat are we spending with Pax8, invoice drilldowns, cost per client or product, spend trend, draft/upcoming charges.
  Vetted Aug 31, 2026
• Pax8 domain model (the distributor, not the tenant)Always when Pax8 is attached. What Pax8 is, its entity model, the purchased-vs-assigned distinction every licensing answer depends on, and the read-vs-write boundary.
  Vetted Aug 31, 2026Always on
• Pax8 provisioning fulfillment — did the order actually deliverDid an order/subscription actually finish provisioning to the MSP's own fulfillment system, is it stuck or failed, what's the unfulfilled backlog, what configuration was entered at checkout, or how many times/how did Pax8 try to deliver the notification.
  Vetted Sep 2, 2026
• Pax8 webhook visibility — what's configured, and why a delivery failedWhat webhooks are configured for this partner, what topics can be subscribed to, why a webhook didn't fire, what Pax8 actually sent on a delivery, or troubleshooting integration/event-delivery issues against Pax8.
  Vetted Sep 2, 2026
• Querying Pax8 — the read surface, paging, and the cheap pathsAlways when Pax8 is attached. How paging and counting work, which filters keep queries cheap, which tools are spec-confirmed rather than live-verified, and the DARK write-tool boundary (orders/subscriptions/quotes/contacts).
  Vetted Aug 31, 2026Always on