Skip to content

Audiences

Build audiences and Lookalike Models, size an audience before building it, and, in an organization billed in credits, quote its price. Conventions apply to every command here.

Create

Build an audience from one or two datasets of filters. See Create Audience.

Flags build a single dataset. Selector flags repeat for more than one value.

FlagInputLookup
--typedataset type, case-insensitiveintuizi audiences create --help
--nameany string
--start-date --end-dateYYYY-MM-DD
--brandPOI: a brand name or id. SKUs: a product brand key or namereference poi brands, reference skus brands --search <name>
--brand-alla search, taking every match (POI or SKUs)same
--categoryname or id, for the types named in --help. SKUs: a product category id or name, which includes every category under itthe catalog for the dataset type, reference skus categories for SKUs
--providerid. Defaults to every provider for the type. Not SKUs, which takes nonereference common signal-providers --data-type <type>
--countryISO-3 codereference common countries --dataset-type <type>
--statestate codereference common states --countries <code>
--citycity namereference common cities --states <code>
--zipcodezip codereference common zipcodes --cities <name>
--filterPOI quality filter: anomalous_devices, anomalous_pois, or strict_gps (POI only, repeatable). Without it the default set anomalous_devices and strict_gps appliesPOI filters
--no-filtersturn every POI quality filter off (sends filters: []). POI only, and not with --filterPOI filters
--frequencyrun the frequency analysis for the dataset type: POI, Apps, or WebDomain
--network-kindhome or mobile (Connectivity only, and required there)
--networka network name, checked against the catalog of the kind (Connectivity only)reference connectivity networks --kind <kind>
--technologyFiber, Cable, DSL, Cable or DSL, Satellite, or Fixed wireless (Connectivity home networks only)
--min-daysthe fewest days of a week a device must use the network, 1 to 7 (Connectivity only, the API’s default is 3)
--merchanta merchant key or name (SKUs only)reference skus merchants
--match-strictnessMatch Strictness, 1 (Very Strict) to 5 (More Reach) (SKUs only, the API’s default is 3)
--device-typethe device type of the purchase click, case-insensitive (SKUs only)reference skus device-values --field type
--device-osthe OS of the purchase click, case-insensitive (SKUs only)reference skus device-values --field os
--device-makethe device make of the purchase click, case-insensitive (SKUs only)reference skus device-values --field make
--device-modelthe device model of the purchase click, case-insensitive (SKUs only)reference skus device-values --field model
--item-price-min --item-price-maxkeep purchased items priced in this range, USD, 0 to 1000000000 (SKUs only)Spend filters
--spend-min --spend-maxkeep home networks whose spend in the picked purchases is in this range, USD, 0 to 1000000000 (SKUs only)Spend filters
--orders-min --orders-maxkeep home networks whose order count in the picked purchases is in this range, 1 to 1000000 (SKUs only)Spend filters
--top-spenderskeep the top share of home networks by spend, in percent: 50, 25, 10, 5, or 1 (SKUs only)Spend filters
--switch-from --switch-toYYYY-MM, both or neither: run Network Switching between the two months. They need --type connectivity. Each month is read as its last full Monday-to-Sunday week
--switch-networkhome (default) or mobile
--switch-min-days2 to 5, default 3: the fewest days of a week a device must be seen on a network for it to be its home network
--filethe whole body as JSON, or - for stdin, forwarded untouched
--dry-runprint the body and create nothing. It still resolves names and, on every type but SKUs, reads the signal-provider catalog, so it needs a token
--wait --timeoutpoll until the build completes or fails, then print the last record read. See Waiting below

Built from flags, a create needs --type, --name, --start-date, and --end-date. Most types also require a --country, and the Body section of Create Audience lists the exceptions. The CLI checks for it before sending only on Origin, so for any other type a missing country is left to the API to reject.

Not every type reads --state, --city, and --zipcode. The location note under the Body section of Create Audience says which types do. The CLI sends them whatever the type, and the API rejects them on a type that does not read them. On --type skus the CLI itself refuses --city and --zipcode before anything is sent (see below).

--type is case-insensitive going in and canonical going out. It accepts the types listed under --type in intuizi audiences create --help. Get Dataset Types shows which types your account can build.

A type builds from flags when every field it requires has a flag. A type that requires a field no flag writes, such as cohort_id, profile_attributes or profile_attribute_groups, or the demographic filters, or that rejects the dates or the signal providers the flags send (on every type but SKUs), goes through --file. --help names those types under --type, and the flags refuse them before anything is read or sent, --dry-run included: the command exits 2 with an error naming the missing field. Completion leaves them out of the --type values. The Body section of Create Audience gives each type’s required fields.

--category resolves against the catalog for the dataset type in use. For WebDomain that is the IAB categories, not the subcategories, and a name resolves to the number in the id column of intuizi reference web iab-categories, which is what Create Audience takes. An IAB code, which --quiet prints, resolves to its id too, even one that other codes contain: IAB1 is taken over IAB10 to IAB19, and an exact name such as Automotive works the same way. On SKUs it resolves against intuizi reference skus categories, as described under --type skus below. intuizi audiences create --help names the types it applies to (SKUs in its --type skus paragraph), and any other type rejects it before anything is sent.

Omitting --provider includes every provider for the dataset type, which is almost always what you want. A --provider the type’s catalog does not list is rejected before anything is created. The CLI reads that catalog first, so the check needs a token. The API would accept such a provider and build an audience that completes with no devices. A --file body lists its own signal_providers.

--brand applies to POI and SKUs, each against its own catalog. Affinity brands travel in their own field, which no flag writes, so that filter needs --file. The affinity and SKUs brand catalogs are different: never send a value of one on the other type.

--type skus targets the devices seen on the home networks of online purchases of a product brand or category, or from a merchant. It needs --merchant, --brand, or --category. The values of one flag are alternatives, and the flags narrow each other on the same order line: a brand with a merchant is that brand bought from that merchant, and a brand with a category is that brand bought in that category. Each --merchant and --brand value is a catalog key or a name, and the CLI sends the key the catalog returns, since the API matches a key exactly. On SKUs, --brand-all reads one page of up to 500 matches and refuses a search that matches more: narrow the search. The dates are the purchase dates, --country and --state are optional, and --match-strictness is sent as max_devices_per_ip only when given.

--category names product categories from intuizi reference skus categories (the Google Product Taxonomy with finer levels, such as Dry Dog Food), sent as categories. A category selects itself and every category under it. A number is taken as the id. A category given twice, by id or by a name that resolves to the same id, is sent once. A name resolves as on any other type, and when several categories match, the error lists each one’s path, since a name such as Accessories sits under several parents. The catalog answers a search with at most 100 rows and is not paged, so a name whose search fills 100 rows is refused even with one exact match: pass the id. The catalog lists only the categories with orders in the last 90 days, so a category without them resolves by id only.

--device-type, --device-os, --device-make, and --device-model filter the device of the purchase click, with values from intuizi reference skus device-values --field type|os|make|model. A value is matched ignoring case and sent as the catalog holds it (IOS), as device_types, device_oses, device_makes, and device_models. The audience is still every device seen on that home network. The catalog answers a search with at most 500 values, the most orders first, and is not paged. A value it does not hold is refused, and so is one whose search fills 500 rows without it, since that cannot be checked: send such a value in a --file body, in upper case as the catalog holds it, since the API matches it exactly. An empty value is refused before anything is sent.

The seven spend flags are sent as the Spend filters of the SKUs block, which define what each one means: --item-price-min and --item-price-max as item_price_min and item_price_max, --spend-min and --spend-max as spend_min and spend_max, --orders-min and --orders-max as orders_min and orders_max, and --top-spenders as spend_top_percent. The rank behind --top-spenders is computed before the spend and orders bounds, so --top-spenders 10 --spend-min 200 keeps the home networks of the top 10 percent that also spent at least 200 USD. Amounts are in USD, written as plain decimal numbers with at most 6 decimal places (such as 150000.55, not 1e3 or 0x10). Each is sent only when given, a zero bound included. A value that is not such a number, a value outside its range, a pair with the minimum above the maximum, and a --top-spenders outside the set are refused before anything is sent, exit 2.

A SKUs dataset takes no signal providers: --provider, --city, --zipcode, --filter, --no-filters, --frequency, and the Connectivity and switching flags are rejected on it before anything is sent, and so are --merchant, --match-strictness, the four --device-* flags, and the seven spend flags on any other type. An AffinityTransactions spend range (spend_min, spend_max) is not written by these flags, so it needs --file. Like every flag that writes the body, the SKUs flags are refused next to --file: the file carries the whole body. See SKUs for what the data is and which datasets it combines with.

intuizi audiences create --type skus \
  --brand dove --merchant "Example Outdoor Store" \
  --country USA --state TX --match-strictness 3 \
  --start-date 2026-10-01 --end-date 2026-10-31 \
  --name "Dove buyers - October 2026" --dry-run

A category with a device filter, here Dog Food (3530) bought from an iOS device, sends "categories": [3530] and "device_oses": ["IOS"]:

intuizi audiences create --type skus --category 3530 --device-os ios \
  --start-date 2026-10-01 --end-date 2026-10-31 \
  --name "Dog food on iOS - October 2026" --dry-run

The top 10 percent of home networks by spend for a category, here Dry Dog Food, sends "spend_top_percent": 10:

intuizi audiences create --type skus --category "Dry Dog Food" --top-spenders 10 \
  --start-date 2026-10-01 --end-date 2026-10-31 \
  --name "Dry dog food top spenders - October 2026" --dry-run

--type origin filters on geography only. --country is required, and intuizi reference common countries --dataset-type Origin lists the countries with Origin data. --brand, --brand-all, and --category are rejected before anything is sent, and DMAs need --file. Origin data is weekly, so the API widens the window to the whole Monday-to-Sunday weeks it touches. The body keeps the dates as given, and stderr names the widened window when it differs.

intuizi audiences create \
  --type poi --brand "Example Coffee" \
  --country USA --state CA --city "San Francisco" \
  --start-date 2026-09-02 --end-date 2026-09-09 \
  --name "Coffee lovers - SF - 1 week" --wait

--type connectivity targets devices by the home internet network or the mobile carrier they used on most days of a week. --network-kind and --country are required, and --network, --technology, and --min-days narrow it. Its data is weekly, so the API widens the window to whole Monday-to-Sunday weeks, as for Origin, and stderr names the widened window.

--switch-from and --switch-to add Network Switching: the devices that kept, changed, and switched their network between the two months. They need --type connectivity: the analysis runs on one Connectivity dataset. Each month is read as its last full Monday-to-Sunday week, both weeks must be built for the dataset’s signal providers, and the dataset keeps its own dates. The analysis requires additional permissions which need to be approved by your Account Manager.

intuizi audiences create \
  --type connectivity --network-kind home --network Starlink \
  --country USA --start-date 2026-10-19 --end-date 2026-10-25 \
  --switch-from 2026-09 --switch-to 2026-10 \
  --name "Starlink - switching Sep to Oct" --wait

Any field no flag writes goes through --file, such as two datasets combined with an operator, the refine, crossvisitation, cross purchase, and network switching blocks, and POI locations and DMAs. See Create an Audience. No flag writes project_id either, so filing the audience under a project also goes through --file.

--frequency runs the frequency analysis for the dataset type as the audience builds: Visitation Frequency on POI, Apps Frequency on Apps, and Web Frequency on WebDomain. It sends the matching key of the analyses block, and any other type rejects it before anything is sent. The analysis counts the distinct days each device was seen, which activations preview sums and an activation’s --freq-min and --freq-max filter on. It cannot be added after the build, so an audience you may want to preview or filter by frequency needs it from the start. The frequency analyses require additional permissions which need to be approved by your Account Manager, and without them the create is refused with a 403.

--filter sends the POI quality filters in the POI dataset’s filters, as described under POI filters. Without --filter, a POI dataset gets the default set: anomalous_devices and strict_gps (GPS Strict Filtering). --filter replaces the default: exactly the filters you pass apply. --no-filters turns every filter off (it sends filters: []). Turn strict_gps off for airports and stadiums, where real crowds can stand on one spot: pass --filter anomalous_devices alone. Values are case-insensitive, and an unknown value, or --filter on any type but POI, is refused before anything is sent.

intuizi audiences create --type poi --brand "Example Offices" --country USA \
  --start-date 2026-06-01 --end-date 2026-08-31 \
  --name "Example Offices - summer" --wait

The day-part variant of the analysis, and a frequency analysis on each dataset of a two-dataset audience, go in the analyses block of a --file body. A day-part audience cannot be previewed. The datastreams array, which asks for data stream visualizations, goes there too, and intuizi reference common datastream-visualizations --dataset-type <type> lists the ids it takes.

intuizi audiences create --file audience.json --wait

Waiting

--wait prints status changes on stderr and the last record read on stdout, whether the build completes, fails, runs past --timeout (default 60m), or gives up after three failed reads in a row. Only Completed exits 0, so branch on the exit code. With --json every outcome prints the API’s envelope, so the status is always .data[0].status.id. A wait that times out or gives up prints the envelope it last polled, and stderr names the intuizi audiences show <id> --wait that resumes it. See The Async Model.

The wait keeps polling through every status that means the build is still running: 100 to 103, 105 DataStreaming, 108 Modeling while a Lookalike Model trains, and 109 Visualizing data streams, which an audience that opts into data stream visualizations reports while it draws them, before 105 and Completed. Any other status ends the wait as a failure.

A timeout, or a wait that gives up, leaves the build running on the server, so resume it with intuizi audiences show <id> --wait rather than creating again. A failed build is final, so there is nothing to resume.

Status 107 Additional Info is one such failure. The build stopped because it cannot be built as defined, and its status will not change. The wait stops there, prints the record, and exits 1 without suggesting a resume. The API read carries only the status, not the reason. Audience Manager shows the reason on the audience, and the error on stderr points there. The usual cause is a date range outside the data loaded for its dataset, so fix the request and create the audience again.

Estimate create

Size an audience without creating it. See Estimate Audience Size.

audiences estimate create takes exactly what Create takes: the same flags, resolved the same way, and the same --file body. It sends the body to Estimate Audience Size, which reports how many devices the audience would hold. Nothing appears in Audience Manager, and no export, cohort, schedule, or activation follows. Swap estimate create for create in the same command line to build the audience that was estimated.

FlagInputLookup
--type --name --start-date --end-date --brand --brand-all --category --provider --country --state --city --zipcode --filteras on Createas on Create
--no-filtersas on Create (POI only, and not with --filter)
--frequencyaccepted and checked as on Create, but an estimate never runs the analysis
--network-kind --network --technology --min-daysas on Create (Connectivity only)as on Create
--merchant --match-strictness --device-type --device-os --device-make --device-model --item-price-min --item-price-max --spend-min --spend-max --orders-min --orders-max --top-spendersas on Create (SKUs only)as on Create
--filethe whole body as JSON, or - for stdin, forwarded untouched
--dry-runprint the body and send nothing. It still resolves names and, on every type but SKUs, reads the signal-provider catalog, so it needs a token
--wait --timeoutpoll until the estimate is completed, blocked, or failed, then print the last record read. See Estimate show
intuizi audiences estimate create \
  --type poi --brand "Example Coffee" \
  --country USA --state CA --city "San Francisco" \
  --start-date 2026-09-02 --end-date 2026-09-09 \
  --name "Coffee lovers - SF - 1 week" --wait

--frequency is there so the command line that builds the audience can be estimated unchanged. It needs the same permissions as on Create, but an estimate never runs an analysis, so it changes neither the figures nor the recipe_hash. --filter and --no-filters are part of the recipe: the filters change both, so estimate with the ones the audience will be built with.

An estimate is metered on the bytes it scans, which count toward the monthly data-scan limit, as the estimate operation on intuizi usage, and an estimate that a worker runs counts toward the build budget. An estimate of one POI dataset at country or state level, of one AffinityTransactions dataset by brands or categories, or of one CTV dataset at country or state level, optionally with vendors or with channel names, usually comes back completed at once, with its figures, method sketch and as_of: a fast answer. It is metered on the bytes it reads and does not count toward the build budget. A POI estimate is fast only with the default set: no filter flag, or exactly --filter anomalous_devices --filter strict_gps. With --no-filters, or any other set, a worker answers it. Any other estimate comes back pending, with no figures, and its status then walks processing to one of completed, blocked, or failed. How long that takes depends on the datasets. It can take minutes, for example AND, OR, NOTIN, and city, DMA, or ZIP requests. An estimate of a recipe your organization is estimating now, or estimated less than 10 minutes ago, shares that run instead: it is not metered, does not count toward the build budget, and reads that run’s status. A fast answer is never shared: the same recipe sent again is usually answered again, often in about a second.

The request carries an Idempotency-Key, as a create does. A retry after a 429 reuses it, and when an estimate gets no response at all, rerunning it with the --idempotency-key stderr printed returns the estimate the first attempt started, if it did, rather than scanning again (see Global flags).

recipe_hash is computed from the operator and datasets only, so the name does not change it. An audience created from the same body carries the same recipe_hash on intuizi audiences show <id> --json, which shows it is the audience that was estimated.

Estimate show

Read one size estimate by id. See Get Audience Estimate.

Takes the id estimate create returned.

FlagInput
--wait --timeoutpoll until the estimate is completed, blocked, or failed, then print the last record read

A completed estimate leads with its figures: uniques, the approximate distinct device count, with a standard error of about 1.6% when method is sketch or approx_set and about 2.3% when it is approx_distinct, then visits, signals, and unique_eips where the dataset types produce them, and as_of. The rest of the estimate object, such as providers and method, follows as rows of its own. Under --json, a fast answer for an AffinityTransactions dataset has no amounts: transactions, amount, online_transactions, and the four ratios (avg_amount_per_scid, avg_transaction_value, avg_transactions_per_scid, and online_share) of .data[0].estimate.totals are null, not 0. A blocked estimate shows its code and reason as blocked, such as OUT_OF_COVERAGE with the dates the data covers, and a failed one explains itself in status_message. --json prints the record as the API returns it, with the figures under .data[0].estimate.

An estimate’s status is a word, not a status id. With --wait, pending and processing keep the wait going, and completed exits 0. blocked and failed are final: the wait stops there, prints the record, and exits 1 with the reason on stderr, naming no command to resume it. So does a status the CLI does not know. A timeout, or a wait that gives up after three failed reads in a row, leaves the estimate running on the server, and stderr names the intuizi audiences estimate show <id> --wait that resumes it.

intuizi audiences estimate show <id> --wait
intuizi audiences estimate show <id> --json | jq '.data[0].estimate.uniques'

Quote

Price an audience in credits before creating it. See Quote Audience.

audiences quote takes exactly what Create takes: the same flags, resolved the same way, and the same --file body. It prints the price in credits, its split over the datasets, and your organization’s credits now and after the build. It creates nothing and is free: it counts toward neither the build budget nor the data-scan limit. Creating the same audience then charges the quoted price.

FlagInputLookup
--type --name --start-date --end-date --brand --brand-all --category --provider --country --state --city --zipcode --filteras on Createas on Create
--no-filtersas on Create (POI only, and not with --filter)
--frequencyaccepted and checked as on Create, but a quote runs nothing
--network-kind --network --technology --min-daysas on Create (Connectivity only)as on Create
--merchant --match-strictness --device-type --device-os --device-make --device-model --item-price-min --item-price-max --spend-min --spend-max --orders-min --orders-max --top-spendersas on Create (SKUs only)as on Create
--filethe whole body as JSON, or - for stdin, forwarded untouched
--dry-runprint the body and quote nothing. It still resolves names and, on every type but SKUs, reads the signal-provider catalog, so it needs a token
intuizi audiences quote \
  --type poi --brand "Example Coffee" \
  --country USA --state CA --city "San Francisco" \
  --start-date 2026-09-02 --end-date 2026-09-09 \
  --name "Coffee lovers - SF - 1 week"

Quotes answer only for an organization billed in credits. Any other organization gets the API’s 403 before the body is checked. Until SKUs has a credit price, a quote of an audience with a SKUs dataset answers 422 (“This run cannot be priced in credits yet. Contact your Account Manager.”). A quote has no id, so --quiet is rejected as a usage error.

List

Page through the audiences in your account. See List Audiences.

FlagInput
--searchcontains match on the audience name
--page --per-pagepage through the results

Show

Read one audience by id. See Get Audience.

FlagInput
--wait --timeoutpoll until the build completes or fails, then print the last record read

The wait reads each status as Waiting describes, including 107 and 109, and this is the command that resumes a wait that timed out or gave up.

normalized_payload is the canonical copy of the name, operator, and datasets the audience was created from. A POI dataset that left filters out shows the resolved default set there. The recipe_hash field next to it (.data[0].recipe_hash, not inside normalized_payload) is computed from the operator and datasets only, not the name. Top-level blocks such as crossvisitation, crosspurchase, networkswitching, and analyses are not part of normalized_payload. It is set only on audiences built through Create Audience, which is what audiences create calls. It is null for Lookalike Models, for the audiences a schedule builds each cycle, for audiences built in Audience Manager, and for audiences created before the field existed:

intuizi audiences show <id> --json | jq '.data[0].normalized_payload'

For an audience built with Network Switching, the output after the audience’s own lines shows the analysis: its version and source, the network type, the two weeks with their dates, the device totals, and the largest flows between networks. --json returns every network and every flow.

Delete

Remove one audience. This cannot be undone. See Delete Audience.

A cohort created from a regular audience with cohorts create --audience-id is deleted with it. Cohorts created from a Lookalike Model are not. Deleting a Lookalike Model that is still modeling stops the run. Data an activation already delivered stays where it was delivered.

FlagInput
--yesskip the confirmation prompt. Required when stdin is not a terminal

Lookalike create

Train a model on a completed audience and produce a new one. See Create Lookalike Audience.

Lookalike Models require additional permissions which need to be approved by your Account Manager. That applies to lookalike cancel too. The seed must be completed, must not itself be a lookalike, and must meet the minimum device count in Limits & Quotas.

FlagInputLookup
--nameany string
--source-audience-idthe seed audienceaudiences list
--target-sizedevice count for the resultLimits & Quotas
--signaldata family to learn from, repeatable
--countryISO-3 code, repeatablereference common countries --dataset-type Origin
--statestate code, repeatablereference common states --countries <code>
--exclude-seed-devicesleave the seed’s devices out of the result
--expand-eidsexpand matched devices to their EIDs
--contrast-audience-ida completed, non-lookalike audience other than the seed. The seed’s own id is refused before anything is sent (exit 2)audiences list
--notifyemail the user who created the run when it completes. On by default, and --notify=false turns it off
--filethe whole body as JSON, or - for stdin, forwarded untouched
--dry-runprint the body, create nothing

Built from flags, a Lookalike Model needs --name, --source-audience-id, --target-size, at least one --signal, and at least one --country.

A Lookalike Model draws its candidates from Origin data, which covers only some countries, and the create accepts any country code. A run whose countries have no Origin data fails after it is created, and when only some of them do, the others are left out of the model without an error. Pick the countries from intuizi reference common countries --dataset-type Origin.

The accepted --signal values are on Create Lookalike Audience.

--notify is always sent, so the completion email goes out unless --notify=false is given. A --file body sets notification itself, and the email goes out when it is left out.

intuizi audiences lookalike create \
  --name "Coffee lovers lookalike" --source-audience-id <id> \
  --target-size 500000 --signal poi --signal apps --country USA

lookalike create has no --wait. Training shows as status 108 Modeling, which is not terminal, and intuizi audiences show <id> --wait follows the new audience through it to Completed. See Build a Lookalike Model.

Lookalike cancel

Stop a model run at its next checkpoint. See Cancel Lookalike.

Takes the id lookalike create returned, not the seed’s --source-audience-id:

intuizi audiences lookalike cancel <id>

The run stops at its next checkpoint. Until then the audience reads 108 Modeling, and once the run stops it ends at 400 Error, which is final and never reaches Completed. intuizi audiences show <id> --wait follows a cancelled run to that status and exits 1, as it does for any failed build. A cancel that arrives once the result is already being published is ignored, and the run completes. A run that has already finished cannot be cancelled. To remove a cancelled run from your lists, run intuizi audiences delete <id>. The confirmation on stderr still says the run keeps reading 108 Modeling and not to --wait on it. That note predates the 400 ending, and the intuizi audiences delete <id> it names still removes the run.

Lookalike quote

Price a Lookalike Model in credits before training it. See Quote Lookalike.

lookalike quote takes exactly what Lookalike create takes: the same flags, checked the same way, and the same --file body. A Lookalike Model costs the same for any size. It prints the price and your organization’s credits now and after the run, and trains nothing.

FlagInputLookup
--name --source-audience-id --target-size --signal --country --state --exclude-seed-devices --expand-eids --contrast-audience-id --notifyas on Lookalike createas on Lookalike create
--filethe whole body as JSON, or - for stdin, forwarded untouched
--dry-runprint the body and quote nothing
intuizi audiences lookalike quote \
  --name "Coffee lovers lookalike" --source-audience-id <id> \
  --target-size 500000 --signal poi --signal apps --country USA

Quotes answer only for an organization billed in credits. Any other organization gets the API’s 403 before the body is checked. A quote has no id, so --quiet is rejected as a usage error.