{"id":2211,"date":"2026-02-16T01:49:09","date_gmt":"2026-02-16T01:49:09","guid":{"rendered":"https:\/\/finopsschool.com\/blog\/ri-marketplace\/"},"modified":"2026-02-16T01:49:09","modified_gmt":"2026-02-16T01:49:09","slug":"ri-marketplace","status":"publish","type":"post","link":"http:\/\/finopsschool.com\/blog\/ri-marketplace\/","title":{"rendered":"What is RI marketplace? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide)"},"content":{"rendered":"\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Quick Definition (30\u201360 words)<\/h2>\n\n\n\n<p>RI marketplace is a cloud capability for buying and selling reserved capacity commitments between customers and providers or between customers. Analogy: a secondary market for prepaid subscriptions where unused time slots are resold. Formal: a transactional platform mapping reserved-capacity SKUs to offers, pricing, and transfer rules within cloud billing and entitlement systems.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">What is RI marketplace?<\/h2>\n\n\n\n<p>An RI marketplace is a platform layer in cloud ecosystems that enables transfer, resale, or exchange of reserved commitment products (Reserved Instances, Savings Plans, committed-use discounts) between accounts or customers according to provider rules. It standardizes listing, pricing, matching, and transfer while enforcing policy, billing reconciliation, and entitlement updates.<\/p>\n\n\n\n<p>What it is NOT<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Not a spot market for ephemeral capacity.<\/li>\n<li>Not a guarantee of identical performance after transfer.<\/li>\n<li>Not a replacement for proper capacity planning or autoscaling.<\/li>\n<\/ul>\n\n\n\n<p>Key properties and constraints<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Transactional listings with start and end dates.<\/li>\n<li>Provider-enforced constraints on transferability and SKU compatibility.<\/li>\n<li>Billing reconciliation across accounts and often prorated refunds.<\/li>\n<li>Identity and compliance checks for transfers.<\/li>\n<li>Varies by provider in allowed products, term lengths, and transfer rules.<\/li>\n<li>Not publicly stated details on every provider implementation; check provider docs for exact rules.<\/li>\n<\/ul>\n\n\n\n<p>Where it fits in modern cloud\/SRE workflows<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Finance\/cost engineering owns optimization and marketplace strategy.<\/li>\n<li>Platform\/SRE teams coordinate SKU mapping and entitlement updates.<\/li>\n<li>CI\/CD and deployment pipelines use marketplace insights for capacity planning.<\/li>\n<li>Observability teams connect cost signals to performance telemetry.<\/li>\n<\/ul>\n\n\n\n<p>Text-only \u201cdiagram description\u201d<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Buyer and Seller accounts list and browse SKUs on a marketplace portal or API.<\/li>\n<li>Marketplace matches buyer offers to seller listings.<\/li>\n<li>Provider verifies identity, validates SKU compatibility, and performs billing transfers.<\/li>\n<li>Entitlement store updates reservation mapping to buyer account.<\/li>\n<li>Billing system issues prorated charges or credits.<\/li>\n<li>Monitoring shows changed committed usage and cost signals.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">RI marketplace in one sentence<\/h3>\n\n\n\n<p>A managed exchange for transferring committed cloud capacity between parties while updating billing and entitlements according to provider rules.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">RI marketplace vs related terms (TABLE REQUIRED)<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>ID<\/th>\n<th>Term<\/th>\n<th>How it differs from RI marketplace<\/th>\n<th>Common confusion<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>T1<\/td>\n<td>Spot instances<\/td>\n<td>Short-term auctioned capacity not committed<\/td>\n<td>People confuse cost savings model with resale<\/td>\n<\/tr>\n<tr>\n<td>T2<\/td>\n<td>Savings Plan<\/td>\n<td>Pricing commitment not always transferable<\/td>\n<td>See details below: T2<\/td>\n<\/tr>\n<tr>\n<td>T3<\/td>\n<td>Committed use discount<\/td>\n<td>Provider-level commitment with fixed term<\/td>\n<td>Often assumed transferable like an RI<\/td>\n<\/tr>\n<tr>\n<td>T4<\/td>\n<td>Marketplace resale platform<\/td>\n<td>Same concept in provider context<\/td>\n<td>Varies by provider rules<\/td>\n<\/tr>\n<tr>\n<td>T5<\/td>\n<td>Capacity exchange<\/td>\n<td>Generic term for trading capacity<\/td>\n<td>Not always billing-aware<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\">Row Details (only if any cell says \u201cSee details below\u201d)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>T2: Savings Plans are pricing constructs that apply discounts across usage categories; transferability varies by provider and plan type and is often more restrictive than classic reserved SKUs.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Why does RI marketplace matter?<\/h2>\n\n\n\n<p>Business impact<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Revenue: Providers gain marketplace transaction fees; sellers may recover sunk costs.<\/li>\n<li>Trust: Transparent resale options reduce disputes and stranded spend.<\/li>\n<li>Risk: Misapplied transfers can create billing gaps or compliance issues.<\/li>\n<\/ul>\n\n\n\n<p>Engineering impact<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incident reduction: Properly matching reserved SKUs to workloads reduces surprise cost-driven throttles.<\/li>\n<li>Velocity: Teams can quickly buy capacity commitments without long procurement cycles.<\/li>\n<li>Toil reduction: Automation around resale and entitlement updates lowers manual billing work.<\/li>\n<\/ul>\n\n\n\n<p>SRE framing<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>SLIs\/SLOs: Reserved capacity affects availability when used to guarantee performance tier; SLOs must consider committed capacity.<\/li>\n<li>Error budgets: Planned sales or transfers should account for capacity changes that might consume error budgets.<\/li>\n<li>Toil\/on-call: Marketplace operations that modify entitlements should be automated to avoid on-call interruptions.<\/li>\n<\/ul>\n\n\n\n<p>What breaks in production (realistic examples)<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>A platform team sells a multi-AZ reserved instance and forgets to remap workloads; production autoscaling triggers unexpectedly.<\/li>\n<li>A finance team buys a mismatched region SKU; billing shows savings but workloads stay on on-demand causing unexpected costs.<\/li>\n<li>Transfer fails verification and leaves orphaned credits; reconciliation requires manual support.<\/li>\n<li>A security policy blocks cross-account transfers; entitlements get stuck pending manual approvals.<\/li>\n<li>Automation scripts assume static reservation IDs and break after a transfer.<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Where is RI marketplace used? (TABLE REQUIRED)<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>ID<\/th>\n<th>Layer\/Area<\/th>\n<th>How RI marketplace appears<\/th>\n<th>Typical telemetry<\/th>\n<th>Common tools<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>L1<\/td>\n<td>Billing<\/td>\n<td>Listings, transfers, credits<\/td>\n<td>Billing events and invoices<\/td>\n<td>Billing system<\/td>\n<\/tr>\n<tr>\n<td>L2<\/td>\n<td>Platform<\/td>\n<td>Entitlement mapping to accounts<\/td>\n<td>Reservation mappings<\/td>\n<td>Cloud console<\/td>\n<\/tr>\n<tr>\n<td>L3<\/td>\n<td>Compute<\/td>\n<td>Instance SKU assignments<\/td>\n<td>Utilization metrics<\/td>\n<td>CMDB<\/td>\n<\/tr>\n<tr>\n<td>L4<\/td>\n<td>Kubernetes<\/td>\n<td>Nodepool reserved SKU purchase<\/td>\n<td>Node utilization<\/td>\n<td>Cluster autoscaler<\/td>\n<\/tr>\n<tr>\n<td>L5<\/td>\n<td>Serverless<\/td>\n<td>Commitment applied to function usage<\/td>\n<td>Invocation counts<\/td>\n<td>Provider billing<\/td>\n<\/tr>\n<tr>\n<td>L6<\/td>\n<td>CI CD<\/td>\n<td>Purchase automation tied to pipeline<\/td>\n<td>Pipeline cost logs<\/td>\n<td>Infra as Code<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\">Row Details (only if needed)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>None<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">When should you use RI marketplace?<\/h2>\n\n\n\n<p>When it\u2019s necessary<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You have long-term predictable workloads and need to recover sunk reservation costs.<\/li>\n<li>A business unit decommissions a project before reservation expiry.<\/li>\n<li>You need quick committed coverage without new long-term procurement.<\/li>\n<\/ul>\n\n\n\n<p>When it\u2019s optional<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>For short-term experiments where spot and autoscaling suffice.<\/li>\n<li>When savings are marginal compared to operational cost of managing transfers.<\/li>\n<\/ul>\n\n\n\n<p>When NOT to use \/ overuse it<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>For highly variable workloads favoring spot or pay-as-you-go.<\/li>\n<li>When transfer rules impose significant complexity or compliance burdens.<\/li>\n<li>For small dollar amounts where transaction fees negate savings.<\/li>\n<\/ul>\n\n\n\n<p>Decision checklist<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>If utilization &gt;70% and term remaining &gt;3 months -&gt; consider listing.<\/li>\n<li>If workload stability is low and autoscaling covers demand -&gt; avoid listing.<\/li>\n<li>If cross-account transfer meets compliance and identity checks -&gt; proceed.<\/li>\n<li>If transfer fees will eliminate &gt;25% of expected refund -&gt; evaluate alternatives.<\/li>\n<\/ul>\n\n\n\n<p>Maturity ladder<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Beginner: Manual listing via console and basic cost tracking.<\/li>\n<li>Intermediate: Automated listing and entitlement mapping with CI\/CD hooks.<\/li>\n<li>Advanced: Policy-as-code for transfer approvals, observability tied to SLOs, and automated optimization with ML suggestions.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">How does RI marketplace work?<\/h2>\n\n\n\n<p>Components and workflow<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Listing interface (portal\/API) where sellers create offers with SKU, term, price, and constraints.<\/li>\n<li>Marketplace matching engine accepting buyer offers or direct purchases.<\/li>\n<li>Validation service ensuring SKU compatibility, identity, and policy compliance.<\/li>\n<li>Billing engine to calculate prorated refunds and future charges.<\/li>\n<li>Entitlement store updating reservation ownership and mapping to accounts.<\/li>\n<li>Notifications and reconciliation processes for finance and operations.<\/li>\n<\/ol>\n\n\n\n<p>Data flow and lifecycle<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Creation: Seller lists reserved SKU with price and constraints.<\/li>\n<li>Discovery: Buyers search and filter on SKU, term, region.<\/li>\n<li>Purchase: Buyer initiates purchase; marketplace validates.<\/li>\n<li>Transfer: Provider updates entitlement mapping and billing.<\/li>\n<li>Post-transfer: Monitoring and reconciliation run; refunds or credits appear.<\/li>\n<\/ul>\n\n\n\n<p>Edge cases and failure modes<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Partial transfer where billing and entitlement diverge.<\/li>\n<li>Transfer blocked by cross-account permission or compliance check.<\/li>\n<li>Seller cancels listing after buyer purchase due to race conditions.<\/li>\n<li>Billing rounding errors causing small orphan credits.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Typical architecture patterns for RI marketplace<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Portal + API + event-driven ledger: Use when multiple integrations and automated workflows needed.<\/li>\n<li>Embedded marketplace within billing system: Use when tight billing reconciliation required.<\/li>\n<li>Cross-account exchange with broker service: Use when organizational policies require brokered approvals.<\/li>\n<li>Programmatic optimization engine paired with marketplace: Use when automated buy\/sell decisions are driven by algorithms.<\/li>\n<li>Hybrid on-prem proxy for multi-cloud enterprises: Use when central finance manages multiple providers.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Failure modes &amp; mitigation (TABLE REQUIRED)<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>ID<\/th>\n<th>Failure mode<\/th>\n<th>Symptom<\/th>\n<th>Likely cause<\/th>\n<th>Mitigation<\/th>\n<th>Observability signal<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>F1<\/td>\n<td>Transfer stuck<\/td>\n<td>Listing shows pending forever<\/td>\n<td>Identity or policy block<\/td>\n<td>Manual approval and retry<\/td>\n<td>Pending transfer events<\/td>\n<\/tr>\n<tr>\n<td>F2<\/td>\n<td>Billing mismatch<\/td>\n<td>Credits not applied<\/td>\n<td>Reconciliation job failed<\/td>\n<td>Rerun reconciliation<\/td>\n<td>Invoice delta alerts<\/td>\n<\/tr>\n<tr>\n<td>F3<\/td>\n<td>Partial entitlement<\/td>\n<td>Only some SKUs moved<\/td>\n<td>SKU mismatch<\/td>\n<td>Validate SKU mapping<\/td>\n<td>Entitlement diff metrics<\/td>\n<\/tr>\n<tr>\n<td>F4<\/td>\n<td>Race condition<\/td>\n<td>Double sale recorded<\/td>\n<td>Concurrency bug<\/td>\n<td>Locking and idempotency<\/td>\n<td>Duplicate transaction logs<\/td>\n<\/tr>\n<tr>\n<td>F5<\/td>\n<td>Unauthorized transfer<\/td>\n<td>Unexpected ownership change<\/td>\n<td>Misconfigured IAM<\/td>\n<td>Rollback and audit<\/td>\n<td>Security audit logs<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\">Row Details (only if needed)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>None<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Key Concepts, Keywords &amp; Terminology for RI marketplace<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Reserved Instance \u2014 A time-bound capacity commitment \u2014 Reduces per-unit cost \u2014 Assuming static workload.<\/li>\n<li>Savings Plan \u2014 Flexible pricing commitment \u2014 Can cover multiple SKUs \u2014 Misunderstood as always transferable.<\/li>\n<li>SKU \u2014 Stock keeping unit for instance types \u2014 Identifies product and pricing \u2014 Ensure exact match across accounts.<\/li>\n<li>Entitlement \u2014 Ownership record for reservation \u2014 Determines billing application \u2014 Orphan entitlements cause gaps.<\/li>\n<li>Prorated refund \u2014 Partial refund when selling mid-term \u2014 Aligns seller compensation \u2014 Rounding causes small deltas.<\/li>\n<li>Marketplace listing \u2014 Public offer for resale \u2014 Contains price and constraints \u2014 Expired listings create confusion.<\/li>\n<li>Listing fee \u2014 Transaction fee taken by provider \u2014 Affects net seller proceeds \u2014 Often non-trivial.<\/li>\n<li>Transfer validation \u2014 Policy checks before ownership changes \u2014 Ensures compliance \u2014 Can block valid transfers.<\/li>\n<li>Billing reconciliation \u2014 Process matching transfers to invoices \u2014 Critical for finance accuracy \u2014 Manual fixes are slow.<\/li>\n<li>Identity verification \u2014 Ensures buyer\/seller identity \u2014 Prevents fraud \u2014 Adds delay.<\/li>\n<li>Cross-account transfer \u2014 Move reservation across accounts \u2014 Useful for organizational changes \u2014 IAM misconfig causes failure.<\/li>\n<li>SKU mapping \u2014 Aligning instance SKUs to entitlement records \u2014 Needed for correct application \u2014 Mistmatches lead to on-demand usage.<\/li>\n<li>Refund window \u2014 Time allowed for seller cancellation \u2014 Influences cash flow \u2014 Short windows cause rushed decisions.<\/li>\n<li>Brokered sale \u2014 Marketplace uses broker for approval \u2014 Adds governance \u2014 Increases turnaround time.<\/li>\n<li>Provider fee \u2014 Marketplace commission \u2014 Reduces seller returns \u2014 Often percent-based.<\/li>\n<li>Elasticity \u2014 Application scaling behavior \u2014 Affects reservation suitability \u2014 High elasticity favors pay-as-you-go.<\/li>\n<li>Capacity planning \u2014 Forecast of resource needs \u2014 Drives reservation buy\/sell decisions \u2014 Poor planning wastes money.<\/li>\n<li>Orphan credits \u2014 Small unused credits post-transfer \u2014 Hard to apply manually \u2014 Requires reconciliation.<\/li>\n<li>Account consolidation \u2014 Merging accounts may require transfer \u2014 Marketplace can assist \u2014 Policy constraints apply.<\/li>\n<li>Instance family \u2014 Grouping of SKUs \u2014 Impacts interchangeability \u2014 Cross-family mismatches are invalid.<\/li>\n<li>Convertible reservation \u2014 Reservation type that allows instance changes \u2014 More flexible but complex \u2014 Transfer rules vary.<\/li>\n<li>Zonal reservation \u2014 Reserved capacity for specific zone \u2014 Higher availability but less portable \u2014 Misapplied zones cause failures.<\/li>\n<li>Regional reservation \u2014 Spread across region \u2014 More portable \u2014 May not map to zonal needs.<\/li>\n<li>Term length \u2014 Duration of reservation \u2014 Longer gives more savings \u2014 Longer term reduces flexibility.<\/li>\n<li>Renewal policy \u2014 Auto-renew behavior \u2014 Avoids lapses \u2014 Need to disable before resale.<\/li>\n<li>Listing TTL \u2014 Time-to-live for a listing \u2014 Controls exposure \u2014 Too long clutters marketplace.<\/li>\n<li>Pricing floor \u2014 Minimum acceptable price \u2014 Protects sellers \u2014 Too high reduces sales.<\/li>\n<li>Matching engine \u2014 Component matching buyers and sellers \u2014 Optimizes trades \u2014 Poor matching increases latency.<\/li>\n<li>Audit trail \u2014 Immutable log of transfers \u2014 Required for compliance \u2014 Missing trail impedes audits.<\/li>\n<li>API quota \u2014 Rate limits on marketplace calls \u2014 Affects automation \u2014 Exceeding causes failures.<\/li>\n<li>Event-driven ledger \u2014 Real-time transfer events \u2014 Enables automation \u2014 Event loss causes drift.<\/li>\n<li>Policy-as-code \u2014 Automated governance for transfers \u2014 Ensures compliance \u2014 Misconfigured policies block valid trades.<\/li>\n<li>ML optimization \u2014 Automated buy\/sell suggestions \u2014 Can improve ROI \u2014 Requires quality data.<\/li>\n<li>Cost allocation tag \u2014 Tags mapping reservations to teams \u2014 Critical for chargeback \u2014 Missing tags create disputes.<\/li>\n<li>Reconciliation delay \u2014 Time between transfer and invoice update \u2014 Creates interim discrepancies \u2014 Monitor closely.<\/li>\n<li>Secondary market \u2014 Generic term for resale exchanges \u2014 Not identical to provider marketplace \u2014 Terms differ.<\/li>\n<li>Settlement \u2014 Final financial processing of transfer \u2014 Completes transaction \u2014 Delays affect cash flow.<\/li>\n<li>Cancellation policy \u2014 Rules for listing withdrawal \u2014 Protects buyers \u2014 Sellers may be penalized.<\/li>\n<li>Compliance check \u2014 Regulatory verification step \u2014 Ensures legal transfer \u2014 Failing checks halts transfer.<\/li>\n<li>Idempotency token \u2014 Prevents double transactions \u2014 Required for safe automation \u2014 Missing tokens cause duplicates.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">How to Measure RI marketplace (Metrics, SLIs, SLOs) (TABLE REQUIRED)<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>ID<\/th>\n<th>Metric\/SLI<\/th>\n<th>What it tells you<\/th>\n<th>How to measure<\/th>\n<th>Starting target<\/th>\n<th>Gotchas<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>M1<\/td>\n<td>Transfer success rate<\/td>\n<td>Percent successful transfers<\/td>\n<td>Success events over attempts<\/td>\n<td>99%<\/td>\n<td>Provider retries mask failures<\/td>\n<\/tr>\n<tr>\n<td>M2<\/td>\n<td>Reconciliation lag<\/td>\n<td>Time until billing matches transfer<\/td>\n<td>Event to invoice delta<\/td>\n<td>&lt;48h<\/td>\n<td>Batch invoice windows vary<\/td>\n<\/tr>\n<tr>\n<td>M3<\/td>\n<td>Net recovered value<\/td>\n<td>Money returned after fees<\/td>\n<td>Sum refunds minus fees<\/td>\n<td>See details below: M3<\/td>\n<td>Prorations and rounding<\/td>\n<\/tr>\n<tr>\n<td>M4<\/td>\n<td>Listing time-to-sale<\/td>\n<td>Time from listing to purchase<\/td>\n<td>Listing created to sold<\/td>\n<td>&lt;14 days<\/td>\n<td>Seasonality affects sale time<\/td>\n<\/tr>\n<tr>\n<td>M5<\/td>\n<td>Orphan credit count<\/td>\n<td>Unapplied small credits<\/td>\n<td>Count of unmatched credits<\/td>\n<td>&lt;5 per account<\/td>\n<td>Small amounts often ignored<\/td>\n<\/tr>\n<tr>\n<td>M6<\/td>\n<td>Entitlement drift rate<\/td>\n<td>Fraction of reservations misapplied<\/td>\n<td>Misapplied entitlements \/ total<\/td>\n<td>&lt;1%<\/td>\n<td>SKU mapping complexity<\/td>\n<\/tr>\n<tr>\n<td>M7<\/td>\n<td>Automation coverage<\/td>\n<td>Percent of marketplace ops automated<\/td>\n<td>Automated ops\/total ops<\/td>\n<td>80%<\/td>\n<td>Edge cases may need manual<\/td>\n<\/tr>\n<tr>\n<td>M8<\/td>\n<td>Cost per transaction<\/td>\n<td>Operational cost per sale<\/td>\n<td>Op cost divided by transactions<\/td>\n<td>Reduce over time<\/td>\n<td>Hidden manual reconciliation<\/td>\n<\/tr>\n<tr>\n<td>M9<\/td>\n<td>Time-to-resolve failed transfer<\/td>\n<td>Mean time to remediation<\/td>\n<td>Failure detection to resolution<\/td>\n<td>&lt;24h<\/td>\n<td>Manual approvals extend time<\/td>\n<\/tr>\n<tr>\n<td>M10<\/td>\n<td>Policy rejection rate<\/td>\n<td>Percent transfers rejected by policy<\/td>\n<td>Rejections\/attempts<\/td>\n<td>&lt;2%<\/td>\n<td>Strict policies can prevent valid trades<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\">Row Details (only if needed)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>M3: Net recovered value measures seller proceeds after provider fees and taxes. Compute using ledger refunds minus transaction fees and any taxes. Watch for prorated refunds that span invoice cycles.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Best tools to measure RI marketplace<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">Tool \u2014 Cloud provider billing APIs<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What it measures for RI marketplace: Transfer events, refunds, invoices.<\/li>\n<li>Best-fit environment: Native provider environments.<\/li>\n<li>Setup outline:<\/li>\n<li>Enable billing API access.<\/li>\n<li>Export billing events to object store.<\/li>\n<li>Stream events to analytics pipeline.<\/li>\n<li>Strengths:<\/li>\n<li>Native accuracy and timeliness.<\/li>\n<li>Provider trustworthiness for billing.<\/li>\n<li>Limitations:<\/li>\n<li>Provider rate limits.<\/li>\n<li>Format and semantics differ by provider.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Tool \u2014 SIEM \/ Audit log platform<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What it measures for RI marketplace: Transfer validation and security events.<\/li>\n<li>Best-fit environment: Organizations requiring compliance.<\/li>\n<li>Setup outline:<\/li>\n<li>Ingest marketplace events.<\/li>\n<li>Create retained audit indices.<\/li>\n<li>Alert on policy violations.<\/li>\n<li>Strengths:<\/li>\n<li>Audit-ready logs.<\/li>\n<li>Security correlation.<\/li>\n<li>Limitations:<\/li>\n<li>Volume and retention costs.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Tool \u2014 Cost optimization platforms<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What it measures for RI marketplace: Sell\/buy recommendations, recovered value.<\/li>\n<li>Best-fit environment: Cost engineering teams.<\/li>\n<li>Setup outline:<\/li>\n<li>Connect billing sources.<\/li>\n<li>Enable marketplace recommendation module.<\/li>\n<li>Configure policy thresholds.<\/li>\n<li>Strengths:<\/li>\n<li>Automated insights.<\/li>\n<li>Cross-account view.<\/li>\n<li>Limitations:<\/li>\n<li>Black-box recommendations require validation.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Tool \u2014 Observability platform (metrics\/traces)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What it measures for RI marketplace: Entitlement drift impact on performance.<\/li>\n<li>Best-fit environment: SRE and platform teams.<\/li>\n<li>Setup outline:<\/li>\n<li>Instrument entitlement change events as metrics.<\/li>\n<li>Correlate with utilization and latency metrics.<\/li>\n<li>Build dashboards.<\/li>\n<li>Strengths:<\/li>\n<li>Correlates operational impact.<\/li>\n<li>Real-time alerts possible.<\/li>\n<li>Limitations:<\/li>\n<li>Needs disciplined tagging.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Tool \u2014 Data warehouse \/ analytics<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What it measures for RI marketplace: Historical trends and modeling.<\/li>\n<li>Best-fit environment: Finance analytics.<\/li>\n<li>Setup outline:<\/li>\n<li>ETL billing and marketplace events.<\/li>\n<li>Build models for sale latency and net proceeds.<\/li>\n<li>Run ML for pricing suggestions.<\/li>\n<li>Strengths:<\/li>\n<li>Flexible analysis.<\/li>\n<li>Long-term trends.<\/li>\n<li>Limitations:<\/li>\n<li>Latency and cost.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Recommended dashboards &amp; alerts for RI marketplace<\/h3>\n\n\n\n<p>Executive dashboard<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Panels: Net recovered value, Monthly transfer volume, Average time-to-sale, Policy rejection rate.<\/li>\n<li>Why: High-level health and ROI visibility for stakeholders.<\/li>\n<\/ul>\n\n\n\n<p>On-call dashboard<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Panels: Active pending transfers, Failed transfers with error codes, Time-to-resolve, Recent reconciliation anomalies.<\/li>\n<li>Why: Quick triage for operational responders.<\/li>\n<\/ul>\n\n\n\n<p>Debug dashboard<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Panels: Last 100 transfer events, Entitlement diffs, In-flight reconciliation jobs, Billing ledger tail.<\/li>\n<li>Why: Deep investigation for engineers.<\/li>\n<\/ul>\n\n\n\n<p>Alerting guidance<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Page vs ticket: Page for transfer blocking critical production capacity or security breaches; ticket for reconciliation lag under threshold.<\/li>\n<li>Burn-rate guidance: If recovered value deviation suggests more than 25% of expected savings lost in 7 days, raise priority.<\/li>\n<li>Noise reduction tactics: Deduplicate duplicate transfer events, group alerts by account, suppress transient failures with short backoff.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Implementation Guide (Step-by-step)<\/h2>\n\n\n\n<p>1) Prerequisites\n   &#8211; Billing API access and permissions.\n   &#8211; Identity and IAM roles for transfers.\n   &#8211; Policy definitions for allowed transfers.\n   &#8211; Observability integrations.<\/p>\n\n\n\n<p>2) Instrumentation plan\n   &#8211; Emit events for listing creation, purchase, transfer start, transfer success\/failure, refund issued.\n   &#8211; Tag events with account, SKU, region, term, and correlation ID.<\/p>\n\n\n\n<p>3) Data collection\n   &#8211; Stream marketplace events to central message bus.\n   &#8211; Persist events into data warehouse and observability platform.\n   &#8211; Ensure durable storage for audit trails.<\/p>\n\n\n\n<p>4) SLO design\n   &#8211; Define SLOs like transfer success rate and reconciliation lag.\n   &#8211; Map SLOs to error budgets and escalation paths.<\/p>\n\n\n\n<p>5) Dashboards\n   &#8211; Build executive, on-call, and debug dashboards.\n   &#8211; Include trend and per-account views.<\/p>\n\n\n\n<p>6) Alerts &amp; routing\n   &#8211; Route critical alerts to on-call platform.\n   &#8211; Use policy-as-code checks to reduce false positives.\n   &#8211; Implement escalation based on time-to-resolve.<\/p>\n\n\n\n<p>7) Runbooks &amp; automation\n   &#8211; Create runbooks for failed transfers, policy rejections, and reconciliation mismatches.\n   &#8211; Automate approvals where safe and auditable.<\/p>\n\n\n\n<p>8) Validation (load\/chaos\/game days)\n   &#8211; Run game days simulating transfer failure, reconciliation delay, and orphan credits.\n   &#8211; Validate alerting and runbook efficacy.<\/p>\n\n\n\n<p>9) Continuous improvement\n   &#8211; Review postmortem and SLO burn.\n   &#8211; Revisit automation thresholds and policies monthly.<\/p>\n\n\n\n<p>Pre-production checklist<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Billing API ingest validated.<\/li>\n<li>IAM and identity verification flow tested.<\/li>\n<li>Test transfer between sandbox accounts.<\/li>\n<li>Dashboard panels populated with test data.<\/li>\n<li>Runbooks authored and reviewed.<\/li>\n<\/ul>\n\n\n\n<p>Production readiness checklist<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>SLOs and alerts configured.<\/li>\n<li>Automation covers routine transfers.<\/li>\n<li>Audit trail retention configured.<\/li>\n<li>Stakeholder notification flows defined.<\/li>\n<li>Reconciliation jobs scheduled and monitored.<\/li>\n<\/ul>\n\n\n\n<p>Incident checklist specific to RI marketplace<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Capture correlation ID and transfer logs.<\/li>\n<li>Check policy rejections and IAM errors.<\/li>\n<li>Validate billing ledger for expected entries.<\/li>\n<li>Escalate to finance if refund disputes occur.<\/li>\n<li>Apply rollback or compensating transfer if needed.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Use Cases of RI marketplace<\/h2>\n\n\n\n<p>1) Decommissioned project\n&#8211; Context: Team shuts down service mid-term.\n&#8211; Problem: Sunk reservation cost.\n&#8211; Why marketplace helps: Recover value by selling remaining term.\n&#8211; What to measure: Net recovered value and time-to-sale.\n&#8211; Typical tools: Billing API, cost optimization tool.<\/p>\n\n\n\n<p>2) Org restructure\n&#8211; Context: Account consolidation across business units.\n&#8211; Problem: Reservations sit in old accounts.\n&#8211; Why marketplace helps: Transfer entitlements to new owning account.\n&#8211; What to measure: Entitlement drift rate.\n&#8211; Typical tools: Provider console, IAM.<\/p>\n\n\n\n<p>3) Capacity rightsizing\n&#8211; Context: Overprovisioned EC2 fleet.\n&#8211; Problem: Excess reserved capacity.\n&#8211; Why marketplace helps: Sell larger reservations and rebuy smaller ones.\n&#8211; What to measure: Cost per transaction and recovered value.\n&#8211; Typical tools: Analytics and marketplace API.<\/p>\n\n\n\n<p>4) Rapid scaling commitment\n&#8211; Context: New product forecasts demand.\n&#8211; Problem: Procurement lag for commitments.\n&#8211; Why marketplace helps: Quick procurement from marketplace sellers.\n&#8211; What to measure: Transfer success rate and utilization.\n&#8211; Typical tools: Marketplace portal and CI\/CD hooks.<\/p>\n\n\n\n<p>5) Compliance-driven transfer\n&#8211; Context: Data residency requires account moves.\n&#8211; Problem: Reservations need to match regional accounts.\n&#8211; Why marketplace helps: Resell and repurchase in compliant accounts.\n&#8211; What to measure: Policy rejection rate.\n&#8211; Typical tools: Policy-as-code, billing APIs.<\/p>\n\n\n\n<p>6) Cost arbitrage for finance\n&#8211; Context: Sellers aim to recoup costs.\n&#8211; Problem: Transaction fees and pricing unknown.\n&#8211; Why marketplace helps: Market sets price; finance recovers value.\n&#8211; What to measure: Net recovered value and average price.\n&#8211; Typical tools: Analytics, broker services.<\/p>\n\n\n\n<p>7) Temporary capacity alignment\n&#8211; Context: Seasonal demand spike.\n&#8211; Problem: Short-term commitment required.\n&#8211; Why marketplace helps: Buy short-remaining-term reservations.\n&#8211; What to measure: Listing time-to-sale and utilization.\n&#8211; Typical tools: Marketplace listings.<\/p>\n\n\n\n<p>8) Platform migration\n&#8211; Context: Moving workloads between instance families.\n&#8211; Problem: Existing reservations tied to old family.\n&#8211; Why marketplace helps: Sell old family reservations then re-commit.\n&#8211; What to measure: Orphan credit count and reconciliation lag.\n&#8211; Typical tools: Cost optimization platforms.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Scenario Examples (Realistic, End-to-End)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Scenario #1 \u2014 Kubernetes nodepool reserved SKU transfer<\/h3>\n\n\n\n<p><strong>Context:<\/strong> An organization runs multiple clusters; a cluster is decommissioned but nodepool reservations remain.<br\/>\n<strong>Goal:<\/strong> Reassign reservations to active clusters without downtime.<br\/>\n<strong>Why RI marketplace matters here:<\/strong> Recover cost and reapply entitlements to active clusters.<br\/>\n<strong>Architecture \/ workflow:<\/strong> Marketplace listing created for zone\/regional node SKUs; buyer account purchases; entitlement mapped to buyer; cluster autoscaler now benefits from commitments.<br\/>\n<strong>Step-by-step implementation:<\/strong> <\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Identify reserved SKUs tied to cluster.<\/li>\n<li>Tag reservations and export listing details.<\/li>\n<li>Create listing via marketplace API.<\/li>\n<li>Buyer purchases and entitlement updated.<\/li>\n<li>Update cluster autoscaler mapping and validate node tenancy.\n<strong>What to measure:<\/strong> Entitlement drift rate, transfer success rate, node utilization post-transfer.<br\/>\n<strong>Tools to use and why:<\/strong> Billing API, cluster autoscaler, observability platform.<br\/>\n<strong>Common pitfalls:<\/strong> SKU mismatches across zones; autoscaler unaware of entitlement changes.<br\/>\n<strong>Validation:<\/strong> Simulate node replacement and verify billing shows committed usage.<br\/>\n<strong>Outcome:<\/strong> Cost recovered and active clusters use reallocated discounts.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Scenario #2 \u2014 Serverless\/managed-PaaS scenario<\/h3>\n\n\n\n<p><strong>Context:<\/strong> A SaaS team moves workloads to provider-managed PaaS functions but has leftover compute reservations.<br\/>\n<strong>Goal:<\/strong> Monetize or shift commitments to match serverless consumption.<br\/>\n<strong>Why RI marketplace matters here:<\/strong> Convert unused compute commitments into value or repurchase appropriate commitments.<br\/>\n<strong>Architecture \/ workflow:<\/strong> Seller lists compute reservations; finance uses proceeds to purchase provider-managed commitment or apply to serverless if provider supports mapping.<br\/>\n<strong>Step-by-step implementation:<\/strong> <\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Audit compute reservations vs serverless spend.<\/li>\n<li>List compute reservations on marketplace.<\/li>\n<li>Use downstream proceeds to buy serverless commitments if supported.<\/li>\n<li>Track billing to ensure serverless discounts applied.\n<strong>What to measure:<\/strong> Net recovered value, reconciliation lag, serverless discount application rate.<br\/>\n<strong>Tools to use and why:<\/strong> Billing API and cost analytics.<br\/>\n<strong>Common pitfalls:<\/strong> Providers may not allow direct mapping from compute refunds to serverless commitments.<br\/>\n<strong>Validation:<\/strong> Confirm serverless billing discounts post-purchase.<br\/>\n<strong>Outcome:<\/strong> Reduced net waste and aligned commitments.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Scenario #3 \u2014 Incident-response\/postmortem scenario<\/h3>\n\n\n\n<p><strong>Context:<\/strong> Transfer process failed during a migration, causing unexpected on-demand costs and an incident.<br\/>\n<strong>Goal:<\/strong> Root cause, restore expected entitlements, and prevent recurrence.<br\/>\n<strong>Why RI marketplace matters here:<\/strong> Entitlement drift caused cost and potential capacity instability.<br\/>\n<strong>Architecture \/ workflow:<\/strong> Incident responders use audit trail, entitlement diffs, and reconciliation jobs to revert or reapply transfers.<br\/>\n<strong>Step-by-step implementation:<\/strong> <\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Triage and identify affected reservations.<\/li>\n<li>Check transfer logs and policy rejection reasons.<\/li>\n<li>Manually remediate entitlement mappings or re-list\/resell as needed.<\/li>\n<li>Update runbooks and add automation for validation.\n<strong>What to measure:<\/strong> Time-to-resolve failed transfer, reconciliation lag, SLO burn.<br\/>\n<strong>Tools to use and why:<\/strong> SIEM, billing API, observability platform.<br\/>\n<strong>Common pitfalls:<\/strong> Lack of correlation IDs and missing audit logs.<br\/>\n<strong>Validation:<\/strong> Restore expected billing signals and confirm no residual on-demand spikes.<br\/>\n<strong>Outcome:<\/strong> Issue resolved, improved automation added.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Scenario #4 \u2014 Cost\/performance trade-off scenario<\/h3>\n\n\n\n<p><strong>Context:<\/strong> A product team must decide between buying a long-term reservation vs using autoscaling and spot instances.<br\/>\n<strong>Goal:<\/strong> Optimize for cost without compromising performance SLOs.<br\/>\n<strong>Why RI marketplace matters here:<\/strong> Offers ability to buy shorter-term reservations in marketplace to test commitments before long-term purchase.<br\/>\n<strong>Architecture \/ workflow:<\/strong> Use marketplace to acquire short-term reservations, measure SLO impact, then decide on longer-term commitments.<br\/>\n<strong>Step-by-step implementation:<\/strong> <\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Run workload under mixed capacity model.<\/li>\n<li>Buy short-remaining-term reservations from marketplace.<\/li>\n<li>Monitor performance and cost for 30 days.<\/li>\n<li>Decide on permanent reservation purchase or revert.\n<strong>What to measure:<\/strong> SLO compliance, net cost per request, transfer success rate.<br\/>\n<strong>Tools to use and why:<\/strong> Observability platform, cost analytics, marketplace API.<br\/>\n<strong>Common pitfalls:<\/strong> Short-term buys may not cover peak traffic.<br\/>\n<strong>Validation:<\/strong> Compare SLO and cost before and after commit.<br\/>\n<strong>Outcome:<\/strong> Data-backed commit decision.<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Common Mistakes, Anti-patterns, and Troubleshooting<\/h2>\n\n\n\n<p>(Note: Symptom -&gt; Root cause -&gt; Fix)<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Symptom: Transfer pending forever -&gt; Root cause: Missing identity verification -&gt; Fix: Complete verification and retry.<\/li>\n<li>Symptom: Credits not applied -&gt; Root cause: Reconciliation job failed -&gt; Fix: Rerun reconciliation and check invoice cycles.<\/li>\n<li>Symptom: Entitlement still in seller account -&gt; Root cause: Transfer succeeded but entitlement mapping failed -&gt; Fix: Reapply entitlement mapping via API.<\/li>\n<li>Symptom: Orphan small credits -&gt; Root cause: Rounding\/proration -&gt; Fix: Aggregate small credits or apply manual consolidation.<\/li>\n<li>Symptom: Duplicate sale recorded -&gt; Root cause: No idempotency token -&gt; Fix: Implement idempotency tokens and locking.<\/li>\n<li>Symptom: High policy rejection rate -&gt; Root cause: Overly strict policy-as-code -&gt; Fix: Review and loosen safe rules.<\/li>\n<li>Symptom: Unexpected on-demand costs -&gt; Root cause: SKU mismatch causes reservations not to be used -&gt; Fix: Validate SKU family and region.<\/li>\n<li>Symptom: Slow time-to-sale -&gt; Root cause: Pricing floor too high -&gt; Fix: Adjust pricing based on market signals.<\/li>\n<li>Symptom: Audit trail incomplete -&gt; Root cause: Event drop during ingestion -&gt; Fix: Add durable event store and retry logic.<\/li>\n<li>Symptom: Automation failing sporadically -&gt; Root cause: API rate limits -&gt; Fix: Add exponential backoff and request batching.<\/li>\n<li>Symptom: Security alert on transfer -&gt; Root cause: IAM misconfiguration -&gt; Fix: Revoke misconfigured roles and rotate keys.<\/li>\n<li>Symptom: Finance disputes over net proceeds -&gt; Root cause: Misapplied fees or tax handling -&gt; Fix: Reconcile ledger and update cost allocation.<\/li>\n<li>Symptom: Marketplace UI shows stale listings -&gt; Root cause: Cache not invalidated -&gt; Fix: Shorten TTL or implement cache invalidation on events.<\/li>\n<li>Symptom: High manual toil -&gt; Root cause: No runbooks and automation -&gt; Fix: Create playbooks and automate common flows.<\/li>\n<li>Symptom: SLO burn after transfer -&gt; Root cause: Capacity change not communicated -&gt; Fix: Notify SRE and update capacity planning SLOs.<\/li>\n<li>Symptom: False-positive alerts on transfer events -&gt; Root cause: No dedupe logic -&gt; Fix: Implement dedupe and group alerts by correlation ID.<\/li>\n<li>Symptom: Marketplace purchases blocked in CI -&gt; Root cause: Missing API credentials in pipeline -&gt; Fix: Use vault-managed credentials.<\/li>\n<li>Symptom: Unexpected tax charges -&gt; Root cause: Incorrect seller region -&gt; Fix: Validate tax settings before listing.<\/li>\n<li>Symptom: Buyer capacity mismatch -&gt; Root cause: Zone-level reservation when buyer needs regional -&gt; Fix: Reevaluate SKU requirements.<\/li>\n<li>Symptom: ML recommendation poor -&gt; Root cause: Bad training data -&gt; Fix: Improve data quality and label historic transactions.<\/li>\n<li>Symptom: Noncompliant transfer -&gt; Root cause: Regulatory restriction not checked -&gt; Fix: Add compliance checks to policy-as-code.<\/li>\n<li>Symptom: High operational cost per transaction -&gt; Root cause: Too much manual reconciliation -&gt; Fix: Automate reconciliation workflow.<\/li>\n<li>Symptom: Observability blindspots -&gt; Root cause: No instrumentation for entitlement events -&gt; Fix: Emit events and metrics.<\/li>\n<li>Symptom: Marketplace outage impacts purchases -&gt; Root cause: Single provider dependency -&gt; Fix: Design retries and alternate procurement paths.<\/li>\n<li>Symptom: Runbook outdated -&gt; Root cause: Postmortem not applied -&gt; Fix: Update runbooks and run playbook training.<\/li>\n<\/ol>\n\n\n\n<p>Observability pitfalls (at least 5 included above)<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Missing entitlement event instrumentation.<\/li>\n<li>No correlation IDs across systems.<\/li>\n<li>No reconciliation metrics.<\/li>\n<li>Overreliance on billing snapshots rather than streaming events.<\/li>\n<li>Alerts triggered on billing noise rather than true state changes.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Best Practices &amp; Operating Model<\/h2>\n\n\n\n<p>Ownership and on-call<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Finance: owns net recovered value and cash reconciliation.<\/li>\n<li>Platform\/SRE: owns entitlement mapping and operational impact.<\/li>\n<li>Security: owns transfer authorization and IAM.<\/li>\n<li>On-call rotations should include a billing\/marketplace owner for critical transfers.<\/li>\n<\/ul>\n\n\n\n<p>Runbooks vs playbooks<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Runbooks: Step-by-step remediation for common failures.<\/li>\n<li>Playbooks: Higher-level decision guides for financial or governance choices.<\/li>\n<li>Keep both versioned and accessible.<\/li>\n<\/ul>\n\n\n\n<p>Safe deployments<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Canary changes to entitlement automation in a sandbox.<\/li>\n<li>Use feature flags for automation.<\/li>\n<li>Rollback paths must update both entitlement and billing mapping.<\/li>\n<\/ul>\n\n\n\n<p>Toil reduction and automation<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Automate common transfers with policy-as-code.<\/li>\n<li>Automate reconciliation and alert if deltas exceed thresholds.<\/li>\n<li>Use idempotency and locking for transactions.<\/li>\n<\/ul>\n\n\n\n<p>Security basics<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Least-privilege IAM for marketplace operations.<\/li>\n<li>Multi-factor approvals for high-value transfers.<\/li>\n<li>Immutable audit logs for compliance.<\/li>\n<\/ul>\n\n\n\n<p>Weekly\/monthly routines<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Weekly: Review pending listings and policy rejections.<\/li>\n<li>Monthly: Reconcile ledger and compute net recovered value.<\/li>\n<li>Quarterly: Review auto-approval policies and SLOs.<\/li>\n<\/ul>\n\n\n\n<p>What to review in postmortems related to RI marketplace<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Transfer timeline and logs.<\/li>\n<li>Reconciliation artifacts and invoice impact.<\/li>\n<li>Policy rejections and manual interventions.<\/li>\n<li>SLO impact and remediation effectiveness.<\/li>\n<li>Automation shortcomings and fixes.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Tooling &amp; Integration Map for RI marketplace (TABLE REQUIRED)<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>ID<\/th>\n<th>Category<\/th>\n<th>What it does<\/th>\n<th>Key integrations<\/th>\n<th>Notes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>I1<\/td>\n<td>Billing API<\/td>\n<td>Provides transfer and invoice events<\/td>\n<td>Data warehouse and observability<\/td>\n<td>Native provider API<\/td>\n<\/tr>\n<tr>\n<td>I2<\/td>\n<td>Cost analytics<\/td>\n<td>Computes recovered value and trends<\/td>\n<td>Billing API and marketplace<\/td>\n<td>See details below: I2<\/td>\n<\/tr>\n<tr>\n<td>I3<\/td>\n<td>Observability<\/td>\n<td>Correlates entitlement with ops metrics<\/td>\n<td>Cluster metrics and traces<\/td>\n<td>Emit entitlement events<\/td>\n<\/tr>\n<tr>\n<td>I4<\/td>\n<td>IAM<\/td>\n<td>Controls transfer permissions<\/td>\n<td>Marketplace and provider roles<\/td>\n<td>Least-privilege required<\/td>\n<\/tr>\n<tr>\n<td>I5<\/td>\n<td>Policy-as-code<\/td>\n<td>Enforces transfer rules<\/td>\n<td>CI and approval workflows<\/td>\n<td>Use for auto approvals<\/td>\n<\/tr>\n<tr>\n<td>I6<\/td>\n<td>Broker service<\/td>\n<td>Centralizes approvals<\/td>\n<td>Finance and security systems<\/td>\n<td>Useful for multi-account orgs<\/td>\n<\/tr>\n<tr>\n<td>I7<\/td>\n<td>Data warehouse<\/td>\n<td>Historical analysis and ML<\/td>\n<td>ETL from billing APIs<\/td>\n<td>Used for pricing models<\/td>\n<\/tr>\n<tr>\n<td>I8<\/td>\n<td>SIEM<\/td>\n<td>Security and audit logging<\/td>\n<td>Audit logs and alerts<\/td>\n<td>Retain for compliance<\/td>\n<\/tr>\n<tr>\n<td>I9<\/td>\n<td>CI\/CD<\/td>\n<td>Automates listing\/purchase flows<\/td>\n<td>Vault and API creds<\/td>\n<td>Protect credentials<\/td>\n<\/tr>\n<tr>\n<td>I10<\/td>\n<td>Automation engine<\/td>\n<td>Runs reconciliation and retry<\/td>\n<td>Message bus and ledger<\/td>\n<td>Idempotency needed<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\">Row Details (only if needed)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>I2: Cost analytics platforms aggregate billing and marketplace data to recommend sell\/buy actions and calculate net recovered value.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently Asked Questions (FAQs)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What exactly is resold on an RI marketplace?<\/h3>\n\n\n\n<p>Reserved capacity commitments such as reserved instances or committed-use discounts; exact product scope varies by provider.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can anyone buy from the RI marketplace?<\/h3>\n\n\n\n<p>Depends on provider rules; often buyers must pass identity and billing checks.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Are marketplace transactions instant?<\/h3>\n\n\n\n<p>Not always; transfers may require validation and reconciliation and can take hours to days.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does resale affect SLA or performance?<\/h3>\n\n\n\n<p>Generally no direct effect but entitlement misapplication can impact cost and perceived capacity.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Are refunds prorated?<\/h3>\n\n\n\n<p>Yes, refunds are typically prorated for remaining term minus fees.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do providers charge fees?<\/h3>\n\n\n\n<p>Yes, providers commonly take transaction fees or commissions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can you automate listings?<\/h3>\n\n\n\n<p>Yes, via APIs, but be mindful of rate limits and idempotency.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How are taxes handled?<\/h3>\n\n\n\n<p>Varies by provider and seller region; not standardized.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What happens if a transfer fails mid-way?<\/h3>\n\n\n\n<p>Billing and entitlements may diverge; run reconciliation and use audit trails to correct.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is marketplace available for serverless commitments?<\/h3>\n\n\n\n<p>Varies by provider; some providers support savings plans applicable to serverless.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do I avoid orphan credits?<\/h3>\n\n\n\n<p>Ensure reconciliation jobs run and small credits are aggregated or applied programmatically.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Who should own marketplace operations?<\/h3>\n\n\n\n<p>Cross-functional ownership: finance for money, platform for entitlements, security for transfers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can transfers be reversed?<\/h3>\n\n\n\n<p>Depends on provider cancellation policies and time windows.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to price a listing?<\/h3>\n\n\n\n<p>Use analytics based on remaining term, usage history, and market demand.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What are common security controls?<\/h3>\n\n\n\n<p>Least-privilege IAM, MFA approvals for high-value transfers, and SIEM monitoring.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How much automation is safe?<\/h3>\n\n\n\n<p>Automate low-risk routine transfers; keep manual approval for high-value or sensitive transfers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to measure success?<\/h3>\n\n\n\n<p>Use metrics like net recovered value, transfer success rate, and reconciliation lag.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How often to review policies?<\/h3>\n\n\n\n<p>Monthly for operational tuning and quarterly for governance review.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p>RI marketplaces offer a practical way to recapture value from reserved commitments and to align capacity purchases with operational needs. They require cross-functional coordination, solid observability, and careful automation to avoid operational and financial surprises.<\/p>\n\n\n\n<p>Next 7 days plan<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Day 1: Enable billing API ingest and export sample marketplace events.<\/li>\n<li>Day 2: Inventory reservations and tag candidate SKUs for sale.<\/li>\n<li>Day 3: Create runbook for failed transfers and test in sandbox.<\/li>\n<li>Day 4: Build basic dashboards for transfer success and reconciliation lag.<\/li>\n<li>Day 5: Configure automation for idempotent listing via API.<\/li>\n<li>Day 6: Run a game day simulating transfer failure and practice runbook.<\/li>\n<li>Day 7: Review outcomes, update policies, and schedule monthly review cadence.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Appendix \u2014 RI marketplace Keyword Cluster (SEO)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Primary keywords<\/li>\n<li>RI marketplace<\/li>\n<li>Reserved instance marketplace<\/li>\n<li>reserve instance resale<\/li>\n<li>cloud reservation marketplace<\/li>\n<li>\n<p>reservation transfer<\/p>\n<\/li>\n<li>\n<p>Secondary keywords<\/p>\n<\/li>\n<li>reserved instance transfer<\/li>\n<li>marketplace reserved SKU<\/li>\n<li>reservation resale platform<\/li>\n<li>committed use resale<\/li>\n<li>\n<p>cloud reservation exchange<\/p>\n<\/li>\n<li>\n<p>Long-tail questions<\/p>\n<\/li>\n<li>how does ri marketplace work<\/li>\n<li>how to sell reserved instances<\/li>\n<li>how to buy reserved instances from marketplace<\/li>\n<li>how to transfer reservations between accounts<\/li>\n<li>what are marketplace listing fees<\/li>\n<li>how long do transfers take<\/li>\n<li>how to reconcile reservation refunds<\/li>\n<li>how to automate reservation listings<\/li>\n<li>how to avoid orphan credits<\/li>\n<li>ri marketplace best practices<\/li>\n<li>how to map skus for reservations<\/li>\n<li>can savings plans be resold<\/li>\n<li>how to measure recovered reservation value<\/li>\n<li>how to set pricing for reserved instance resale<\/li>\n<li>how to handle taxes for reservation resale<\/li>\n<li>how to build entitlement audit trail<\/li>\n<li>how to monitor entitlement drift<\/li>\n<li>how to use marketplace for k8s nodepools<\/li>\n<li>how to validate reservation transfers<\/li>\n<li>\n<p>what to do when transfer stuck<\/p>\n<\/li>\n<li>\n<p>Related terminology<\/p>\n<\/li>\n<li>reserved instance<\/li>\n<li>savings plan<\/li>\n<li>SKU<\/li>\n<li>entitlement<\/li>\n<li>prorated refund<\/li>\n<li>reconciliation<\/li>\n<li>transfer validation<\/li>\n<li>policy-as-code<\/li>\n<li>idempotency token<\/li>\n<li>billing API<\/li>\n<li>audit trail<\/li>\n<li>orphan credit<\/li>\n<li>brokered sale<\/li>\n<li>listing TTL<\/li>\n<li>provider fee<\/li>\n<li>reconciliation lag<\/li>\n<li>net recovered value<\/li>\n<li>entitlement drift<\/li>\n<li>automation engine<\/li>\n<li>cluster autoscaler<\/li>\n<li>capacity planning<\/li>\n<li>cost allocation tag<\/li>\n<li>compliance check<\/li>\n<li>SIEM<\/li>\n<li>data warehouse<\/li>\n<li>ML optimization<\/li>\n<li>marketplace listing<\/li>\n<li>billing ledger<\/li>\n<li>audit logs<\/li>\n<li>transfer success rate<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>&#8212;<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-2211","post","type-post","status-publish","format-standard","hentry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v25.3 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>What is RI marketplace? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide) - FinOps School<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/finopsschool.com\/blog\/ri-marketplace\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"What is RI marketplace? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide) - FinOps School\" \/>\n<meta property=\"og:description\" content=\"---\" \/>\n<meta property=\"og:url\" content=\"https:\/\/finopsschool.com\/blog\/ri-marketplace\/\" \/>\n<meta property=\"og:site_name\" content=\"FinOps School\" \/>\n<meta property=\"article:published_time\" content=\"2026-02-16T01:49:09+00:00\" \/>\n<meta name=\"author\" content=\"rajeshkumar\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"rajeshkumar\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"25 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/finopsschool.com\/blog\/ri-marketplace\/\",\"url\":\"https:\/\/finopsschool.com\/blog\/ri-marketplace\/\",\"name\":\"What is RI marketplace? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide) - FinOps School\",\"isPartOf\":{\"@id\":\"http:\/\/finopsschool.com\/blog\/#website\"},\"datePublished\":\"2026-02-16T01:49:09+00:00\",\"author\":{\"@id\":\"http:\/\/finopsschool.com\/blog\/#\/schema\/person\/0cc0bd5373147ea66317868865cda1b8\"},\"breadcrumb\":{\"@id\":\"https:\/\/finopsschool.com\/blog\/ri-marketplace\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/finopsschool.com\/blog\/ri-marketplace\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/finopsschool.com\/blog\/ri-marketplace\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"http:\/\/finopsschool.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"What is RI marketplace? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide)\"}]},{\"@type\":\"WebSite\",\"@id\":\"http:\/\/finopsschool.com\/blog\/#website\",\"url\":\"http:\/\/finopsschool.com\/blog\/\",\"name\":\"FinOps School\",\"description\":\"FinOps NoOps Certifications\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"http:\/\/finopsschool.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"http:\/\/finopsschool.com\/blog\/#\/schema\/person\/0cc0bd5373147ea66317868865cda1b8\",\"name\":\"rajeshkumar\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\/\/finopsschool.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/787e4927bf816b550f1dea2682554cf787002e61c81a79a6803a804a6dd37d9a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/787e4927bf816b550f1dea2682554cf787002e61c81a79a6803a804a6dd37d9a?s=96&d=mm&r=g\",\"caption\":\"rajeshkumar\"},\"url\":\"http:\/\/finopsschool.com\/blog\/author\/rajeshkumar\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"What is RI marketplace? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide) - FinOps School","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/finopsschool.com\/blog\/ri-marketplace\/","og_locale":"en_US","og_type":"article","og_title":"What is RI marketplace? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide) - FinOps School","og_description":"---","og_url":"https:\/\/finopsschool.com\/blog\/ri-marketplace\/","og_site_name":"FinOps School","article_published_time":"2026-02-16T01:49:09+00:00","author":"rajeshkumar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"rajeshkumar","Est. reading time":"25 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/finopsschool.com\/blog\/ri-marketplace\/","url":"https:\/\/finopsschool.com\/blog\/ri-marketplace\/","name":"What is RI marketplace? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide) - FinOps School","isPartOf":{"@id":"http:\/\/finopsschool.com\/blog\/#website"},"datePublished":"2026-02-16T01:49:09+00:00","author":{"@id":"http:\/\/finopsschool.com\/blog\/#\/schema\/person\/0cc0bd5373147ea66317868865cda1b8"},"breadcrumb":{"@id":"https:\/\/finopsschool.com\/blog\/ri-marketplace\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/finopsschool.com\/blog\/ri-marketplace\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/finopsschool.com\/blog\/ri-marketplace\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"http:\/\/finopsschool.com\/blog\/"},{"@type":"ListItem","position":2,"name":"What is RI marketplace? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide)"}]},{"@type":"WebSite","@id":"http:\/\/finopsschool.com\/blog\/#website","url":"http:\/\/finopsschool.com\/blog\/","name":"FinOps School","description":"FinOps NoOps Certifications","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"http:\/\/finopsschool.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"http:\/\/finopsschool.com\/blog\/#\/schema\/person\/0cc0bd5373147ea66317868865cda1b8","name":"rajeshkumar","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/finopsschool.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/787e4927bf816b550f1dea2682554cf787002e61c81a79a6803a804a6dd37d9a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/787e4927bf816b550f1dea2682554cf787002e61c81a79a6803a804a6dd37d9a?s=96&d=mm&r=g","caption":"rajeshkumar"},"url":"http:\/\/finopsschool.com\/blog\/author\/rajeshkumar\/"}]}},"_links":{"self":[{"href":"http:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/2211","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"http:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=2211"}],"version-history":[{"count":0,"href":"http:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/2211\/revisions"}],"wp:attachment":[{"href":"http:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=2211"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=2211"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/finopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=2211"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}