Public Agent Card

Infinite Audience

This profile reflects information published by the agent provider.

Card passedAuthentication requiredUnsigned card

About this agent

Enrich customer data, discover high-fidelity net-new audiences, and activate them in your channels through an AI agent. Select a skill from this card; skill-specific access is enforced by the server.

LocalMark's observation

LocalMark first listed this public Agent Card on 07 Oct 2026, 05:36 UTC. Its latest card check succeeded. The card declares 19 skills and a JSONRPC interface. LocalMark has not run a production A2A task. Explicitly opted-in synthetic tests are shown separately.

Read the original Agent Card ↗

What LocalMark checked

  • Published Agent Card

    Inspect the source card ↗. The last successful fetch was 21 Nov 2026, 20:12 UTC.

  • Latest card check: passed

    21 Nov 2026, 20:12 UTC · Agent Card validated

  • Advertised endpoint: TLS connection passed

    21 Nov 2026, 20:12 UTC · Valid TLS connection to advertised endpoint host; no A2A request sent This does not test the A2A protocol or run a task.

  • Read-only protocol probe: Authentication required

    21 Nov 2026, 08:11 UTC · Endpoint requires authentication; A2A response not confirmed LocalMark sent no message and did not request task creation.

  • Unsigned card

    This card does not provide a digital signature. Checked 21 Nov 2026, 20:12 UTC.

  • 30-day card check history

    116 of 116 recorded card checks passed in the last 30 days. These are periodic observations, not continuous uptime monitoring.

  • Publisher claim

    No publisher claim has been completed for this listing.

Card availability and a valid signature do not prove provider identity, task performance, or safety. Opt-in synthetic fixture results, if any, are shown separately from these read-only observations.

Advertised connection checks

The selected connection uses an address advertised in the publisher card. Read-only observations do not establish task quality or safety.

  • JSONRPC · 1.0 · Selected connection

    https://a2a.infiniteaudience.ai/a2a

    Authentication required · 21 Nov 2026, 08:11 UTC

    Endpoint requires authentication; A2A response not confirmed

  • JSONRPC · 0.3

    https://a2a.infiniteaudience.ai/a2a

    Authentication required · 21 Nov 2026, 08:11 UTC

    Endpoint requires authentication; A2A response not confirmed

Up to three supported interfaces are checked per cycle. Authentication requirements, unsupported transports and generic HTTP errors are not protocol confirmation.

Repair connection or request a recheck →

Publisher-authorized synthetic tests

Publisher: set up test evidence →

No current fixture result · Not yet checked

A publisher-authorized synthetic test of a dedicated free test endpoint. It does not establish general capability, production task success, safety, ownership, identity, or the behaviour of the advertised A2A endpoint.

Consent: not confirmed.

Recent fixture observations
  • No fixture tests recorded.

Results, consent dates and hashes as JSON · Method, fixtures and publisher opt-in →

Recent card checks

Periodic observations over the last 30 days; they are not continuous uptime monitoring.

Show 12 recent checks
  • Passed · 21 Nov 2026, 20:12 UTC

    Agent Card validated

  • Passed · 21 Nov 2026, 08:11 UTC

    Agent Card validated

  • Passed · 20 Nov 2026, 20:11 UTC

    Agent Card validated

  • Passed · 20 Nov 2026, 08:10 UTC

    Agent Card validated

  • Passed · 19 Nov 2026, 20:09 UTC

    Agent Card validated

  • Passed · 19 Nov 2026, 08:09 UTC

    Agent Card validated

  • Passed · 18 Nov 2026, 20:08 UTC

    Agent Card validated

  • Passed · 18 Nov 2026, 08:07 UTC

    Agent Card validated

  • Passed · 17 Nov 2026, 20:06 UTC

    Agent Card validated

  • Passed · 17 Nov 2026, 08:05 UTC

    Agent Card validated

  • Passed · 16 Nov 2026, 20:04 UTC

    Agent Card validated

  • Passed · 16 Nov 2026, 06:57 UTC

    Agent Card validated

View the 30-day check log as JSON →

Card and signature changes

  • Card changed

    04 Nov 2026, 02:49 UTC · Confirmed published card change: skills_updated, other_card_fields; fingerprint 1101f0b64bb9

  • Card changed

    02 Nov 2026, 08:46 UTC · Confirmed published card change: skills_updated, other_card_fields; fingerprint a936b460af64

View detailed card versions → · Subscribe to card changes

Share this listing

Link to this profile with a status badge that updates from LocalMark checks.

LocalMark status badge

README Markdown:

[![LocalMark status](https://localmark.ai/badge/25.svg)](https://localmark.ai/agents/25)

Card-declared connections

These links come from statements in public Agent Cards. They do not verify common ownership or cooperation.

  • No card-declared connections recorded yet.

View all connections as JSON →

Declared skills 19

  • Account & Balance

    Read existing organization subscription capacity, active reservations, pending consumption, replenishment state, readiness and snapshot freshness. Monetary amounts identify their currency and denomination. Agency-managed organizations receive their own attributed consumption. Requires 'account-read' scope (or account scope for existing API keys).

    accountusagebalance
  • Audience Delivery

    Deliver a saved audience as a download using available organization subscription capacity. Supports CSV, JSON, JSONL and Avro, with explicit output compression. The first successful file-match delivery also consumes its matching capacity. Retained, already-covered deliveries support re-export under existing coverage. Review the pricing skill's capacity estimate before delivery. Requires 'creator' scope.

    audiencesdeliveryactivation
  • Audience Management

    Create and manage audiences: composition wrappers that group one or more segments for delivery. Audiences have no subtype — use segment-management to create typed cohorts. Duplicate an existing audience via the duplicate_audience tool — the duplicate carries the source composition with lineage tracking (parent and root ancestor recorded, segment versions pinned) and starts with a null record count until recounted. Refresh a stale or expired audience via the refresh_audience tool — since an audience is a composition of one or more member segments (possibly mixed subtypes) with no single 'primary' segment, refresh_audience requires a segment_id naming which member to refresh; choose a filter or matched member because custom snapshots require a new internal publication; it refreshes that eligible segment and bumps the audience's own version/expiry, but never any other audience referencing the same segment. Operate on one audience per action. Archival is reversible via archive_audience with restore=true; external agents do not delete audiences. Requires 'creator' scope.

    audiencescompositionmanagement
  • Campaign Lookup

    Read-only campaign inspection: list campaigns or get a single campaign's brief and linked audiences. Pass metadata.campaign_id to supply an active campaign context for the turn. Requires 'discovery' scope.

    campaignsaudiencesworkspace
  • Campaign Management

    Create, update, and archive campaign workspaces, including their campaign brief and goals. Link or unlink audiences from campaigns — a campaign holds many audiences, an audience belongs to at most one. Pass metadata.campaign_id to supply an active campaign context for the turn; audiences created in that turn join it, and segments record it as their origin_campaign_id. Requires 'creator' scope. For read-only campaign list and detail requests, submit under the campaign-lookup skill instead — it only requires 'discovery' scope.

    campaignsaudiencesworkspace
  • Data Catalog

    Browse enrichment attributes, coverage and subscription capacity rates. Discover the available fields before selecting enrichment outputs. Requires 'discovery' scope.

    catalogfieldsenrichment
  • Delivery History

    List existing deliveries for an audience, a file-based match job, or the organization. Filter by status, destination or audience and continue with the returned cursor. Results include record counts, subscription capacity consumption, output format, compression and timestamps. Monetary amounts are denominated in USD. Requires 'discovery' scope.

    deliveryhistorystatus
  • Delivery Status

    Check the status and download URLs for a specific delivery. Poll after initiating a delivery to determine when records are ready. Note: download_urls are short-lived presigned GCS URLs regenerated fresh on every GET — do not cache them. Requires 'discovery' scope.

    deliverystatusdownloads
  • Show all 11 remaining skills
    • Discovery Count

      Count matching records in the audience graph given geo, demographic, behavioral, or custom filter criteria. Accepts saved segment IDs, audience IDs, multi-segment composition, filter_groups, or flat filters. Returns total record count without purchasing records; backend compute usage is recorded as non-commercial telemetry. Requires 'discovery' scope.

      audiencesdiscoverycounts
    • Discovery Crosstab

      Cross-tabulate a population by two categorical dimensions (e.g. state x gender) and return a pivot table of counts. Accepts saved segment IDs, audience IDs, multi-segment composition, filter_groups, or flat filters. Backend compute usage is non-commercial telemetry. Requires 'discovery' scope.

      audiencesdiscoveryanalysis
    • Discovery Lookup

      Return masked sample rows and field metadata for a defined audience without purchasing records. Accepts saved segment IDs, audience IDs, multi-segment composition, filter_groups, or flat filters. Useful for validating filter criteria before committing to a delivery; backend compute usage is non-commercial telemetry. Requires 'discovery' scope.

      audiencesdiscoverysamples
    • Discovery Overlap

      Calculate how many records appear in both of two populations (audiences, segments, or ad-hoc filter sets) and return overlap count, overlap_pct, and demographic deltas. Backend compute usage is non-commercial telemetry. Requires 'discovery' scope.

      audiencesdiscoveryoverlap
    • Identity Resolution & Match History

      Resolve up to 100 contact records synchronously using residential, work or auto spatial matching, or process larger identity files through segment-management. Synchronous matching consumes subscription capacity for matched records when results are returned. File matching consumes capacity with the first successful delivery. Responses include match statistics and monetary consumption estimates in USD. History is available through match-history. Requires 'creator' scope; history reads require 'discovery' scope.

      identitymatchingenrichment
    • Integration Result History

      List or retrieve safe, retained integration activity without exposing private workflow artifacts. Results include provenance, counts, selected fields, subscription capacity source, promotion deadline, and durable Library links. Requires 'discovery' scope.

      integrationshistoryresults
    • Match History

      Retrieve cursor-paginated micro-batch and file matching history from POST /v1/match and POST /v1/match/file. Results include run or match identifiers, counts, match rate, status, timestamps and subscription capacity consumption estimates in USD. File-job matching consumption becomes available after first successful delivery. Requires 'discovery' scope.

      matchinghistorystatus
    • Pricing & Quoting

      Estimate expected and upper-bound subscription capacity for an audience download, denominated in USD. Existing licenses reduce the expected identity component; applicable file matching capacity is included separately. Review both estimates and available capacity before delivery. Saves an estimate for the current audience. Requires 'discovery' scope.

      pricingquotesdelivery
    • Save Integration Result

      Preview saved integration matches, then create or extend a matched Segment using already-settled identities. Confirm the preview and target with the user. A stable request_id makes retries idempotent; this reuses existing enrichment capacity. It does not create an Audience automatically; compose one separately when needed. Requires 'creator' scope.

      integrationssegmentsaudiences
    • Segment Lookup

      Segment inspection: get a demographic breakdown via get_segment_demographics (any subtype — non-filter segments resolve via the same ID-set composition audiences use), list the audiences that reference a segment (with campaign linkage) via get_segment_audiences, or recount via count_segment (runs a fresh BigQuery count for any subtype). Demographics and recount operations record non-commercial compute telemetry. Requires 'discovery' scope.

      segmentsdemographicscounts
    • Segment Management

      Create filter (criteria-based) or matched (uploaded CSV/JSON/JSONL/Avro lists, optionally gzip-compressed and split into same-format shards) segments. Runtime subtypes are filter, matched and custom; custom membership is published through the internal data-team tool. Automated custom generation is not yet available. Matched segments accept residential, work, or auto spatial matching; auto expands commercial workplace inputs. Segments are reusable cohort definitions that can be composed into audiences for delivery. Duplicate any segment via the duplicate_segment tool — the duplicate preserves the subtype and all subtype-specific data (referenced, never recomputed) with lineage tracking; filter duplicates start with a null count while other subtypes carry the source counts, and duplicating a matched segment whose match data is unavailable is rejected with a 409 conflict. Refresh a stale filter or matched segment against the current identity graph via the refresh_segment tool; custom snapshots return 409 CUSTOM_REGENERATION_REQUIRED and need a new internal publication — referencing audiences are never touched; archived segments and matched duplicates that share another segment's data are rejected with a 409. Use patch_segment to rename or replace a filter definition. Operate on one segment per action; archive_segment supports reversible archival and restoration. Requires 'creator' scope. For get_segment_demographics, get_segment_audiences, and count_segment (which require only 'discovery' scope but can meter compute or update cached state), submit under the segment-lookup skill instead.

      segmentscohortsmanagement