- Brand
- Anrok
- Category
- Finance
- Primary Subcategory
- Compliance, Risk & Privacy Operations
Integration details
Description
Use your existing Anrok connection to inspect transactions and tax summaries, customers, products, exemption certificates, filings, and nexus, and perform supported updates when requested.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- Compliance, Risk & Privacy Operations
- Secondary Subcategories
- None listed
- Brand
- Anrok
- Access
- Account required
- First tracked
- 2026-11-20
- Tool count
- 39
- Market
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Not discoverable in ChatGPT yet
ChatGPT now suggests Plugins on its own when they match a user's request, but not every Plugin is being surfaced yet.We haven’t seen Anrok suggested yet. Sign up and we’ll track it, and your Discoverability Score will appear here once ChatGPT starts surfacing it.
What discovery looks like

Get alerts for Anrok
Get updates when Anrok’s Discoverability Score or category rank changes.
Competing in ChatGPT Compliance, Risk & Privacy Operations
View Category39 tools agents can invoke
Archive (deactivate) an exemption certificate by ID so it no longer exempts the customer. Requires an API key with the certificates or sellerIntegration scope.
archive_certificate
Create an exemption certificate for a customer, with the document and the jurisdictions it covers. Returns the new certificate id and a short-lived (1 hour) downloadable fileUrl. Requires an API key with the certificates or sellerIntegration scope, and additionally the customers scope when createCustomerIfMissing is true.
create_certificate
Request an exemption certificate from a customer (optionally emailing them a link). Requires an API key with the certificates or sellerIntegration scope.
create_certificate_request
Create a customer. Requires an API key with the customers or sellerIntegration scope.
create_customer
Create a transaction, or overwrite the existing one with the same id. Persists the transaction and returns the computed tax. Amount inputs go in as minor units (e.g. cents), but every amount in the response is in major units (e.g. dollars). Requires an API key with the transactionsWrite or sellerIntegration scope.
create_or_update_transaction
Create a product with a tax category. Requires an API key with the products or sellerIntegration scope.
create_product
Estimate the tax on a hypothetical sale WITHOUT persisting anything. Returns the tax to collect overall and per line item / jurisdiction. Line item amounts go in as minor units (e.g. cents), but every amount in the response is in major units (e.g. dollars). Requires an API key with the transactionsRead, transactionsWrite, or sellerIntegration scope.
estimate_transaction_tax
Fetch a single exemption certificate by ID. Includes a short-lived (1 hour) downloadable fileUrl for the certificate document. Requires an API key with the certificates or sellerIntegration scope.
get_certificate
Anrok's own currency conversion rates, the ones it uses to convert amounts in its tax calculations, filings, and reports. For each date, returns the latest Anrok rate on or before it: the rate (units of toCurrency per 1 fromCurrency), its effectiveDate, its source, and whether it is final (a non-final rate can still be revised), and optionally converts an amount at that rate. For amounts on a return, pass the return's jurisId and jurisFilingId: some jurisdictions require a particular bank's rate or the rate on the last day of the reporting period, and only then do the rates match the return. Without them, these are the rates Anrok's exposure modeling uses, converting each transaction at the rate for its accounting date: pass the transactions' dates, and as toCurrency the jurisdiction's currency to match the exposure modeling page or the functional currency to match get_nexus_status. Use these rates for the user's tax and sales amounts, such as tax liabilities, filing amounts, transaction totals, and nexus thresholds, including when the latest Anrok rate is older than the date asked about. Do not convert these amounts at a rate recalled from memory. Tell the user the rate, its effective date, and its source. If Anrok has no rate on or before a date, tell the user Anrok has none for that date. Works with any valid API key.
get_currency_conversion_rates
Fetch a single customer by ID. Requires an API key with the customers or sellerIntegration scope.
get_customer
Details for one filing: amounts breakdown (taxable/tax/total/total due: what the return reports as due, not what was paid), status, key dates, obligationType (salesTax or a secondary obligation), remittance transfer method, whether a form was submitted, attached document names, and pendingRefundCredits: the credit carry-forwards for the jurisdiction not yet applied on any return that report under this filing's obligation type (the "Credits not applied on this return" section in the app). These are refunds or credit notes whose negative tax could not be offset against tax due in the same local region; Anrok applies them to a future return automatically. They are not bounded by the filing period: the same credits appear on every filing of that obligation type until applied. Totals are grouped by transaction currency and are negative. To list the credit transactions themselves, call list_transactions with the filingInfo filter, filingAssociationStatus "pendingRefundCredit", and this filing's obligationType (returns of type salesTax, marketplaceFacilitatorSales, invoiceCurrencySales carry them). For the amount remitted on a filed return and the state discount, penalties, interest and other adjustments behind any difference from the tax due, use list_filing_remittances. remittanceTransferMethod says which bank account pays the jurisdiction. "columnBankSfboAccount" and "columnBankIntlWire": Anrok collects the tax into the seller's Column for-benefit-of account and pays the jurisdiction from there (by ACH or international wire). "sellerExternalAccount": the jurisdiction typically debits the seller's own bank account when the return is filed, with no collection through Anrok. "sellerExternalAccountPush": the seller pays from their own bank account. "anrokDisbursementAccount": Anrok pays from its own disbursement account. No method by itself means a payment was missed or went outside the normal filing flow. Requires an API key with the transactionsRead or sellerIntegration scope.
get_filing_summary
Per-jurisdiction nexus status, tax exposure, registration status, and filing info over a date range, with economic-nexus threshold progress and taxDueAmount, the tax Anrok calculated in the range. With an HRIS connected, hrisRecommendationType and hrisRecommendedDate say whether employee locations create or move physical nexus; hrisRequiresAction is true only when they do and the seller has taxable products. summary.hrisIntegrationStatus: Whether employee location data flows in from a connected HRIS. notEnabled = the seller's plan does not include automated physical nexus tracking, so connecting an HRIS would not help; notConnected = no HRIS is connected (the seller can connect one under Data Sources); needsReauth = an HRIS is connected but needs reauthorization, so employee data may be stale; connected = employee locations sync from the HRIS. Set includeBalanceSummary (with a date range) for each remitting jurisdiction's reconciliation row: beginningBalanceAmount + taxDueAmount - taxRemittedAmount - stateDiscountAmount + penaltiesAndInterestAmount + otherAmount = endingBalanceAmount. taxRemittedAmount totals the returns filed in the range, by filed date. To match ledger or bank payments, go return by return with list_filing_remittances, not this total. endingBalanceAmount splits into priorPeriodsBalanceAmount, for periods ended before dateBegin, and currentPeriodsBalanceAmount. If dateBegin starts the earliest unfiled period, currentPeriodsBalanceAmount is tax awaiting a return. priorPeriodsBalanceAmount is not; it is a reconciling item, such as a period filed outside Anrok. All amounts are in the seller's functional currency (currencyCode) except nexusThresholdAmount and nexusSalesAmountNet, in nexusThresholdCurrency. Exposure uses the Anrok rate for each transaction's accounting date, which get_currency_conversion_rates returns without jurisId and jurisFilingId. Pass jurisIds for particular jurisdictions. Requires an API key with the registrations or sellerIntegration scope.
get_nexus_status
Fetch a single product by its external ID. Requires an API key with the products or sellerIntegration scope.
get_product
Totals the seller's tax-collection discrepancies (transactions where the tax the billing system charged differs from the tax Anrok calculated), split into under- and over-collected tax, overall and per jurisdiction. Answers "how much tax did I under-collect this quarter, and where?" and "where is my collection risk?". taxAmountUnderCollected is tax Anrok calculated beyond what was charged (on a refund, tax refunded beyond what Anrok calculated); returns use the calculated tax, so the seller remits it without having collected it. taxAmountOverCollected is tax charged beyond what Anrok calculated. Both are positive and taxCollectionDiscrepancyAmount is their net: report under- and over-collected separately, since the net lets them cancel. totals counts each transaction once. jurisdictions has one row per jurisdiction with a discrepancy, largest under-collection first; a transaction taxed in several jurisdictions counts in full in each, so use totals for the overall figure. Omit dateBegin and dateEndi for all time, including when the user names no period. A totals.transactionCount of 0 means the seller has no discrepancies there: say so plainly. If more than 100,000 transactions match, the tool says so: split the date range, call once per window, and add up the totals and each jurisdiction's rows. Amounts are decimal strings in major units of the seller's functional currency; other currencies are converted at their accounting-date rate. To list the transactions behind a jurisdiction, call list_tax_discrepancies with its jurisId and the same dates. Results are computed live, and the freshness field says so. Requires an API key with the transactionsRead scope.
get_tax_discrepancy_summary
Fetch a single transaction by ID, in full detail: line items, per-jurisdiction tax breakdown, customer, amounts, and the transaction's current version. A voided transaction returns only its status metadata and version -- no line items, tax breakdown, customer or amounts -- so treat those absences as "this transaction is voided", not as a failed or partial fetch. Use search_transactions to find a transaction ID first. Requires an API key with the transactionsRead or sellerIntegration scope.
get_transaction
Aggregated transaction totals (revenue and tax) for the seller over a date range, optionally grouped by time (day/month/quarter/year) and/or jurisdiction. Amounts are decimal strings in major currency units. Use this for revenue/tax summaries rather than listing individual transactions. For refunded amounts over a period, use the *Refunded fields. For how many refunds, or which transactions were refunds, use search_transactions with refundsOnly. Pass dateBegin and dateEndi on every call unless groupBy is "total" and groupByJuris is true, which may omit both to get one row per jurisdiction over all time and no totals. For an all-time total, pass dateBegin "0001-01-01" and dateEndi "9999-12-31" and read totals; do not add preTaxAmountNet across jurisdiction rows, because a transaction can count in more than one jurisdiction. Requires an API key with the transactionsRead scope.
get_transaction_summary
Counts the seller's unprocessed transactions (invoices or credit notes that failed to import or recalculate and never became a transaction), grouped by error type (the default), by source integration (the billing system) or by jurisdiction. Use this instead of paging through list_unprocessed_transactions to answer how many failed, why, or from which system; use the list for the individual rows. Takes the same filters as the list. isExact is true when the rows cover every matching transaction. When it is false the rows cover only a capped subset of the matches, in no particular order (not the newest and not a random sample): treat totalCount as a floor ("N+") and do not rank groups or compute proportions from the rows. totalCount is omitted for jurisdiction, because one error can belong to several jurisdictions, so do not add jurisdiction counts together; a row with a null jurisId counts errors that have no jurisdiction yet, and when jurisIds is given only those jurisdictions get rows. A totalCount of 0 means no unprocessed transactions matched the filters (with no filters, the seller has none). includeEstimatedAmounts adds an estimated USD amount per row, as a decimal string, or null when no error in the row had an estimate; amounts are only summed over the first matching errors, so expect isExact false for very large sellers. Only active (non-archived) unprocessed transactions are covered; archived ones are not queryable by any tool. Requires an API key with the transactionsRead or sellerIntegration scope.
get_unprocessed_transaction_summary
List the seller's Anrok billing statements: what Anrok charged the seller for its own service, the same statements as the Billing page in the Anrok app. These are not invoices from the seller's own billing system. Returns, per statement and newest billing period first: id, name, type (recurringMonthly, recurringYearly, filing for the fee on one return Anrok filed, or oneTime), the billing period, status (processing: under review or being collected, not yet paid; paid; failed: payment failed for a reason the seller has to fix, such as an invalid bank account), taxAmount (sales tax Anrok charged on its fees), totalAmount (including that tax), and currencyCode. Pass periodDateBegin and periodDateEndInclusive for the statements whose billing period overlaps a date range; an empty list means there are none in that range. Anrok charges a flat monthly fee plus basis points on the prior month's billable sales, calculated in the second week of each month, so a statement is usually charged the month after its billing period. A bank descriptor ending in "PMT INFO: YYYYMM Statement" is the Anrok billing statement for billing period YYYYMM, not a tax payment. Line items and the billable transactions behind a statement are not returned; they are on the statement's page in the app, which can export the transactions. Its Print button gives a printable copy of the statement, which the browser can save as a PDF. Not available to Viewer (read-only) members. Requires an API key with the transactionsRead or sellerIntegration scope.
list_anrok_billing_statements
List the authenticated seller's exemption certificates. Supports pagination via a cursor and filtering by customer, status, or expiry date. For certificates expiring in the next N days, set filter.expiresOnOrAfter to today and filter.expiresOnOrBefore to today plus N days, with no status filter: the expiringSoon status only covers the next 60 days. Requires an API key with the certificates or sellerIntegration scope.
list_certificates
List the authenticated seller's customers. Supports pagination via a cursor. Requires an API key with the customers or sellerIntegration scope.
list_customers
The bank transfers Anrok made for sales tax returns outside the US, with the amounts the bank actually moved, as the app's bank transfer sections show them. Each return has the totals collected from the seller (collectedAmount), remitted to the jurisdiction (remittedAmount), processing fees, and refundAmount: the part of the collection the payment did not use, which Anrok owes back to the seller (the app's "Refund amount"). refundedAmount is how much of the refundAmount completed refund transfers have sent back so far; the rest is still pending, so never call more than refundedAmount refunded. Collections include an exchange-rate buffer, so collectedAmount normally exceeds remittedAmount plus fees. Each transfer has a type (collection; remittance; refund, the unused collection sent back to the seller; remittanceRefund, money the jurisdiction returned; or transferFeeReimbursement), date, status, and amount. A remittance also has the tax it paid in local currency (taxPaidAmount), the exchange rate the bank applied (fxRate, units of taxPaidCurrencyCode per 1 currencyCode), and its processing fees (processingFeesAmount), which are not part of the remittance's amount. Totals count only completed transfers (isCompleted). Use this for what was actually collected, paid, or refunded in USD outside the US, and to reconcile against bank records. Report these amounts rather than converting local-currency amounts with get_currency_conversion_rates, whose reference rates won't match the rate the bank applied. Pass filing for one return, or transferDateRangeInclusive for every return with a transfer dated in that range. A return in a range comes with all its transfers, even those dated outside it, so total a period's cash movement from only the transfers dated in it. US returns are not covered; for what was remitted on them, use list_filing_remittances. Returns paid from the seller's own account have none. Requires an API key with the transactionsRead or sellerIntegration scope.
list_filing_bank_transfers
What was paid on each filed return of the obligation types that can carry a payment (salesTax, marketplaceFacilitatorSales and invoiceCurrencySales; obligationType names it): the amount Anrok recorded as remitted (taxRemittedAmount) next to the tax due, any state discount taken (such as a timely-filing or vendor discount), penalties and interest, and other amounts, in the seller's functional currency, one row per return filed in a filed-date range, with the date Anrok recorded it as filed. Use this to see whether a return was paid in full or why the payment differs from the tax due. To reconcile against a ledger, bank statement, or payment records, match each payment to the specific returns it pays: one payment can cover several returns and can post days or weeks after the return's filed date, so totals over the same window can differ even when every return was paid in full. For a date window, widen the filed-date range by a filing period on each side so a payment early in the window can be matched to a return filed before it. Report a discrepancy only once it is tied to specific returns and payments, and don't explain a difference with causes the data doesn't show. For a return filed in another currency, the amounts here are converted to the functional currency at Anrok's reference rate, not what the bank actually moved; for the USD actually collected, remitted, and refunded on a return outside the US, use list_filing_bank_transfers. Requires an API key with the transactionsRead or sellerIntegration scope.
list_filing_remittances
List the IDs of transactions rolled up into a specific filing, identified by its jurisId and jurisFilingId (from list_filings). Requires an API key with the transactionsRead or sellerIntegration scope.
list_filing_transaction_ids
List the authenticated seller's filings. Supports pagination via a cursor and filtering by jurisdiction, filing-period end date, who files (filter.filingFlowTypes), frequency (filter.frequencies), currency (filter.currencyCodes), filed state (filter.isFiled — set false for only still-open returns), or status (filter.statuses — use ["sellerReview"] for the returns awaiting the seller's approval). Each filing includes its jurisId, jurisFilingId, name, obligationType, period, status, statusDisplayName, dueDate, reviewByDate (the deadline for approving a return in seller review), isFiled, and whether it is still automatically updated for transaction changes. obligationType is the return type (salesTax, or a secondary obligation such as marketplaceFacilitatorSales). Returns of type salesTax, marketplaceFacilitatorSales, invoiceCurrencySales carry pending refund credits; pass the filing's obligationType to list_transactions to list them. For what was paid (remitted) on filed returns, use list_filing_remittances. This listing carries no amounts: for tax due per filing, totals, or filtering by amount, use search_filings. Requires an API key with the transactionsRead or sellerIntegration scope.
list_filings
List the jurisdictions the seller has, each with its registration status (not started, draft, processing, action required, or complete), whether the seller is remitting, and key dates. A processing registration needs nothing from the seller: Anrok is handling it and will reach out about any follow-up items. It does not say whether Anrok or the jurisdiction has it, so never say which one it is waiting on. Requires an API key with the registrations or sellerIntegration scope.
list_jurisdictions
List the source-to-Anrok product ID mappings for a seller integration. Requires an API key with the products or sellerIntegration scope.
list_product_id_mappings
List the seller's available product tax categories (standard and custom). Anrok does not pick a category for the seller: when helping the user choose one, open with the caveat that this is general information, not tax advice for their business. Requires an API key with the products or sellerIntegration scope.
list_product_tax_categories
List the seller's products. Supports pagination via a cursor. Requires an API key with the products or sellerIntegration scope.
list_products
List transactions with a tax-collection discrepancy (where the tax owed does not equal the tax collected). Returns, per transaction (all amounts in major units): transactionId, taxAmountToCollect (tax owed), taxAmountCollected (tax actually collected — 0 means none was collected), taxCollectionDiscrepancyAmount (the uncollected tax = owed minus collected), the accounting date, and the currency. taxAmountToCollect is the tax Anrok calculated; taxAmountCollected is the tax the billing system actually charged on the invoice, as reported to Anrok. Returns include these transactions at Anrok's calculated tax, not the amount collected, so a positive discrepancy is tax the seller will remit without having collected it from the customer. Refunds and credit notes carry negative amounts, so there a positive discrepancy means the billing system refunded more tax than Anrok calculated. Filter client-side on a zero taxAmountCollected for the "collected nothing" subset. Supports an optional accounting-date filter (dateBegin/dateEndi) and cursor pagination. To scope to a jurisdiction pass jurisId; to scope to a specific return pass jurisId + jurisFilingId (from list_filings). Amounts are always per-transaction totals: a transaction taxed in multiple jurisdictions shows its full discrepancy in each jurisdiction's scoped result (amounts are not apportioned per jurisdiction). Requires an API key with the transactionsRead scope.
list_tax_discrepancies
List the authenticated seller's transactions. Supports pagination via a cursor and filtering by last-modified time or by filing association. Unfiltered or filtered by last-modified time, results come oldest-modified first and transactions modified in the last hour are not returned, so this is a reliable change feed rather than a live view. The filingInfo filter lists either the transactions rolled up into a given filing, or the credit carry-forwards for a jurisdiction and obligation type that are not yet applied on any return (filingAssociationStatus "pendingRefundCredit" with the filing's obligationType; get_filing_summary reports their count and totals). filingInfo results come in accounting-date order and include recently modified transactions. Each row carries full transaction detail, including every line item and its product and tax category, so pages are large and slow: reach for this tool when you need that detail or a change feed, and prefer search_transactions when you are scanning or filtering many transactions by date, jurisdiction, customer or VAT status, or get_transaction_summary when you only need bucketed aggregates. Requires an API key with the transactionsRead scope.
list_transactions
Lists the seller's unprocessed transactions, newest first (by accounting date when a date range is given, otherwise by when the error was recorded): invoices or credit notes that failed to import from a billing integration or failed a recalculation, and so never became a transaction. Each row has the billing-system invoiceId, the Anrok transactionId (for recalculation errors), the customer, date, error type, the offending value (errorField), the raw message, the source integration, an invoice link and whether it is retryable. This is a separate table from processed transactions: search_transactions and list_transactions have no error filter, so use this tool for questions about failed, errored, or unprocessed transactions. Filter by date range, error types, source integration, jurisdictions, amount or a specific invoiceId (a billing-system invoice ID or an Anrok transaction ID; for a transaction ID also check get_transaction, since a recalculation error belongs to a transaction that exists, and combine what both find), and page with the cursor. For counts or breakdowns, use get_unprocessed_transaction_summary instead of paging. Only active (non-archived) unprocessed transactions are covered; archived ones are not queryable by any tool. For remediation guidance, follow up with search_help_center_articles: query "edit transaction addresses" for address-type errors (missingAddress, missingAddressCountry, unsupportedAddressCountry, malformedAddress), "configure new product IDs" for missingProductId or unknownProductId, "reconfigure product IDs" for productTaxCategoryNotSupportedForJuris, or "resolve unprocessed transactions" otherwise. Requires an API key with the transactionsRead or sellerIntegration scope.
list_unprocessed_transactions
Identify an Anrok record ID by its type (derived from the ID prefix) and fetch the record when it is fetchable by that ID — e.g. a certificate ID ("ctec…") is fetched directly. Customers, products, transactions, and filings are keyed by external IDs you assign, so this tool identifies the type and points you at the right dedicated tool instead. Works with any valid API key.
lookup_by_id
Fuzzy-match the seller's customers against a name and return ranked candidates, each with a similarity score (0-1), plus a bestMatch and an overall confidence (high/medium/low/none). Use this to resolve a name (e.g. from a document) to a customer when an exact match is not certain; it tolerates word-order and partial-term differences, but candidates are still found by substring search, so a misspelled single word may return no match. For an exact customer ID, use get_customer instead. Requires the customers or sellerIntegration scope.
match_customer
Ranks the seller's customers (top, biggest or best customers; most purchases, orders or transactions; most revenue or tax) over a period with no customer IDs needed, and gives each one's transaction count, total, pre-tax revenue, tax, first and last transaction dates, and most recent VAT validation status. Answers "who are my top 10 customers?", "which customers have I sold more than $5M to in California in the last year?", "which customers generate the most tax?" and "who has the most transactions?". Set sortBy to choose the ordering (default pre-tax revenue), jurisId to limit to one jurisdiction, and minPreTaxRevenue to return only customers whose net pre-tax revenue is at least a threshold. With a jurisId, amounts and tax are that jurisdiction only. Amounts are net of refunds, decimal strings in major units of the seller's functional currency; other currencies are converted at their accounting-date rate. Transactions with no customer are not included, so an empty customers list means no customer-attributed transactions matched, not that the seller has no sales. Results are computed live, and the freshness field says so. On very large sellers a wide range can be cut off; if it is, narrow by jurisdiction or use a shorter period and say the answer covers only that part, and do not add shorter windows together, since a customer can be in the top N or over a threshold for the whole period without making the cut in any one window. Use get_customer for one customer's details. Requires an API key with the transactionsRead scope.
rank_customers
Search for customers by name or ID; returns up to 8 matches (id and name). Use this to look up a customer ID before fetching their transactions or certificates. Requires an API key with the customers or sellerIntegration scope.
search_customers
Search the seller's filings (returns) with each one's tax due, a match count, optional per-currency totals, and a tax-due amount filter. Filters: status, filed state, due date, period, jurisdiction, who files (filingFlowTypes), frequency, currency, and amountMin/amountMax. list_filings is the lean listing; use this one when the question is about amounts: "which open filings owe more than $50k" (amountMin plus currencyCodes with exactly one code), "how much do I still owe" (isFiled false with includeTotals true), or "my largest returns" (sortBy latestAggregateTaxDueAmount). totalTaxDueAmount is a decimal string in major units of the filing's currencyCode. A null totalTaxDueAmount means the amount was not computed yet because the return is still open or its cached amount is stale, not that nothing is owed; say so when quoting amounts. To get the number, call get_filing_summary for one return, or add amountMin or amountMax with one currencyCode to this search: every return inside that range comes back with its amount. Never add amounts across currencies. amountMin and amountMax are inclusive. For strictly "more than X", pass X plus one minor unit, e.g. "50000.01" for more than $50,000. With amountMin or amountMax the result is not paginated: totalCount is the exact number of matching filings and at most limit of them are returned, so raise limit or narrow the filters when totalCount is larger. Without an amount filter the list is cursor-paginated and totalCount reads 1001 when more than 1000 filings match. When totals is null, totalsUnavailableReason says why: tooManyFilings (more than 1000 match; narrow by jurisdiction, status or date range, then retry) or resolutionFailed (retry, or narrow the filters). Requires an API key with the transactionsRead or sellerIntegration scope.
search_filings
Search the Anrok Help Center (help.anrok.com) for articles answering a "how do I…" question about using Anrok. Returns up to 3 relevant article titles, URLs, and bodies (or a support pointer if nothing matches). Works with any valid API key.
search_help_center_articles
List the account's marketplace vendors, most recently added first: the connected accounts (e.g. Stripe Connect accounts) that sell through its marketplace. Use this to find the vendor ID to pass as marketplaceVendorId to search_transactions. Search by the vendor's business name or account ID. A name is null until an invoice carrying it has been ingested, so if a name finds nothing, list the vendors and match by name or ask for the account ID. If several match, ask which one is meant. An empty list means the account has no marketplace vendors. hasMore is true when more vendors exist than were returned; narrow the query rather than paging. Requires an API key with the transactionsRead or sellerIntegration scope.
search_marketplace_vendors
Search processed transactions by date range, jurisdiction, customer, vendor, seller role, city/postal code, VAT-validation status, return association, filing (return), or currency, sorted by accountingDate, taxDate or amount. sortBy "taxDate" requires jurisIds; without a named jurisdiction, ask which to use or sort by accountingDate and say so. Returns cursor-paginated rows and "totals" summing amount, preTaxAmount, taxAmount, taxCollectionDiscrepancyAmount and refunds over the FULL filtered set. Always use totals, never the returned rows; for "how many transactions" use totals.transactionCount. totals is null, with totalsUnavailableReason saying why, in two cases: "searchUnbounded" when no date range, customerId, vendor, facilitator role or filing filter was passed (add one; only dates count with filingAssociationStatuses); and "transactionCountOverLimit" when more than 100,000 transactions match. For "transactionCountOverLimit", split the date range into shorter windows with the same filters and add their totals; for an all-time or open-ended request, first find the earliest and latest matching accountingDate (limit 1, sortBy "accountingDate", sortDirection "asc" then "desc") and split only between them. With "conversionRateNotFound", amounts and currencyCode in totals are null but counts are exact; no filter change helps. To see transactions behind a return, pass its jurisId and jurisFilingId as filing; filingIsFiled: false finds transactions on unfiled returns. taxCollectionDiscrepancyAmount is tax Anrok calculated minus tax charged, and returns use the calculated amount; hasTaxCollectionDiscrepancy keeps only mismatches. Use get_tax_discrepancy_summary for under- and over-collected totals by jurisdiction, and list_tax_discrepancies for per-transaction amounts. Use get_transaction_summary for date-range totals or time- or jurisdiction-bucketed aggregates; it cannot filter by customer, VAT status, return association, filing or tax discrepancy. Requires an API key with the transactionsRead scope.
search_transactions
Anrok ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Anrok's ChatGPT Plugin discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Anrok alternatives on ChatGPT?
As of 2026-11-20, Anrok competes with AdSimple Consent Manager, AirMason Handbook Audit, ClearPolicy, ComplyOnSite, ConsentLayer, CookieYes, D&B Risk Analytics, DoctillaQM and 20 more in ChatGPT Compliance, Risk & Privacy Operations, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.