AWS Marketplace Metering Service

Name: AWS Marketplace Metering Service API
Brand: AWS Marketplace Metering Service
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsBilling Subscriptionshmac4 EndpointsREST

For Agents

Submit Marketplace usage records for SaaS, AMI, and container products and resolve customer identifiers from registration tokens.

Connect the AWS Marketplace Metering Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Marketplace Metering Service, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AWS Marketplace Metering Service API.

Submit hourly usage records for AMI products with MeterUsage

Batch submit usage records for multiple SaaS customers with BatchMeterUsage

Resolve a customer registration token into a customer identifier and product code

GET STARTED

Start building with AWS Marketplace Metering Service API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AWS Marketplace Metering Service, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS Marketplace Metering Service, keeping it validated and agent-ready. The Metering API lets AWS Marketplace sellers submit usage records for paid products billed through AWS — SaaS, AMI, and container offerings priced by hourly, monthly, or custom dimensions. MeterUsage submits per-instance usage; BatchMeterUsage reports usage for SaaS subscriptions across multiple customers; ResolveCustomer turns a registration token into a customer identifier; RegisterUsage handles entitlement-based container products.

Use Cases

Patterns agents use AWS Marketplace Metering Service API for, with concrete tasks.

★ SaaS Subscription Metering

SaaS sellers on AWS Marketplace meter customer usage on custom dimensions (active users, storage GB, API calls) and submit usage with BatchMeterUsage, which accepts up to 25 customer records per call. Each record specifies the customer identifier returned from ResolveCustomer, the dimension name, and the quantity. AWS aggregates these records and bills the buyer through their AWS account.

Call BatchMeterUsage with ProductCode='abc123' and a UsageRecords array of 25 customer entries each specifying CustomerIdentifier, Dimension='active_users', Quantity, and Timestamp

AMI Hourly Billing

AMI sellers run MeterUsage from instances of their paid product to record hourly usage on dimensions like 'small', 'medium', or feature flags. The call comes from inside the AMI itself, signed with the IAM role attached to the instance, and reports the dimension consumed in the previous hour. Marketplace handles aggregation, taxation, and customer billing.

Call MeterUsage from an EC2 instance with ProductCode, Timestamp set to the start of the previous hour, UsageDimension='medium', and UsageQuantity=1

Customer Registration Resolution

When a buyer subscribes to a SaaS product on Marketplace, AWS redirects them with a registration token. The seller's web app exchanges that token for the persistent customer identifier and product code via ResolveCustomer, then stores the identifier so future BatchMeterUsage calls reference the correct buyer. The exchange is one-time and idempotent per token.

Call ResolveCustomer with the RegistrationToken passed in the marketplace redirect, then store the returned CustomerIdentifier and ProductCode in our user database

AI Agent Billing Operations

Billing agents call Marketplace Metering through Jentic to submit usage records on a schedule, retry transient failures, and reconcile counts against internal usage stores. Jentic isolates the AWS keys and exposes the four metering operations as discoverable tools so the agent can answer 'submit yesterday's user counts to Marketplace' without learning the AWS SDK.

Search Jentic for 'submit marketplace usage', load BatchMeterUsage, and execute it with the previous day's customer-by-customer counts on dimension 'active_users' grouped from internal usage logs

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for aws marketplace metering service, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=AWSMPMeteringService.MeterUsage

Submit per-instance usage record for an AMI product

POST

/#X-Amz-Target=AWSMPMeteringService.BatchMeterUsage

Submit a batch of usage records for SaaS customers

POST

/#X-Amz-Target=AWSMPMeteringService.ResolveCustomer

Exchange a registration token for a customer identifier

POST

/#X-Amz-Target=AWSMPMeteringService.RegisterUsage

POST

/#X-Amz-Target=AWSMPMeteringService.MeterUsage

Submit per-instance usage record for an AMI product

POST

/#X-Amz-Target=AWSMPMeteringService.BatchMeterUsage

Submit a batch of usage records for SaaS customers

POST

/#X-Amz-Target=AWSMPMeteringService.ResolveCustomer

Exchange a registration token for a customer identifier

POST

/#X-Amz-Target=AWSMPMeteringService.RegisterUsage

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS keys are stored encrypted in the Jentic vault. Each Marketplace Metering call is signed with Signature Version 4 server-side, and IAM scoping restricts the agent to the metering and resolve-customer actions only — so usage submission cannot drift into broader account access.

Intent-based discovery

Agents search by intent (e.g. 'submit marketplace usage' or 'resolve a marketplace customer token') and Jentic returns the relevant Metering operation with its input schema, including the UsageRecords shape required by BatchMeterUsage.

Time to first call

Direct integration: under a day for IAM, but extra time on retry logic for UnprocessedRecords. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS Marketplace Catalog Service

Catalog defines the products and dimensions Metering reports against

Use Catalog when the agent needs to define or update product dimensions; use Metering when it needs to submit actual usage records against those dimensions.

Complementary

AWS License Manager

License Manager governs entitlements that Metering may report usage against

Use License Manager when the agent needs to check or distribute entitlements; use Metering when it needs to record actual consumption against a paid product.

Alternative

Stripe

Stripe Billing handles usage-based billing outside AWS Marketplace

Choose Stripe when the seller bills customers directly off-Marketplace; choose AWS Marketplace Metering when usage must be billed through the buyer's AWS account.

FAQs

Specific to using AWS Marketplace Metering Service API through Jentic.

Why is there no official OpenAPI spec for AWS Marketplace Metering?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Marketplace Metering Service via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AWS Marketplace Metering API use?

The API uses AWS Signature Version 4 (HMAC) with an access key ID and secret access key scoped via IAM. AMI sellers typically call from instances using an instance-profile role with aws-marketplace:MeterUsage permissions; SaaS sellers call from server-side workloads. Through Jentic, those credentials live in the encrypted vault and are signed in server-side.

Can I submit usage for multiple customers in a single call?

Yes. BatchMeterUsage accepts up to 25 UsageRecords in one call, each containing CustomerIdentifier, Dimension, Quantity, and Timestamp. The response surfaces successful records and a separate UnprocessedRecords array — the seller is expected to retry unprocessed entries with backoff.

What are the rate limits for the AWS Marketplace Metering API?

AWS does not publish hard request-per-second limits in this spec, but BatchMeterUsage caps at 25 records per call and per-region throttles apply to high-volume submitters. Submit usage hourly or daily and batch records to stay well within service limits.

How do I submit SaaS usage through Jentic?

Search Jentic for 'submit marketplace usage' to surface BatchMeterUsage. Load the schema with the Jentic SDK (pip install jentic), execute it with your ProductCode and the array of UsageRecords for each metered customer, and inspect the Results and UnprocessedRecords fields in the response.

Is the AWS Marketplace Metering API free?

Yes — submitting metering records has no API fee. AWS Marketplace charges sellers a percentage of revenue on the underlying products being metered, but the metering calls themselves do not incur a usage charge.