<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Tierux Blog</title>
  <subtitle>Practical guides on in-app purchase verification, Google Play billing migration, MCP agent setup, and the economics of subscription apps.</subtitle>
  <link href="https://tierux.com/blog" rel="alternate" type="text/html"/>
  <link href="https://tierux.com/blog/atom.xml" rel="self"/>
  <id>https://tierux.com/blog</id>
  <updated>2026-06-28T00:00:00Z</updated>
  <author>
    <name>Tierux Team</name>
  </author>
  <entry>
    <title>Setting up MCP for AI agent billing</title>
    <link href="https://tierux.com/blog/mcp-ai-agent-billing-setup" rel="alternate" type="text/html"/>
    <id>https://tierux.com/blog/mcp-ai-agent-billing-setup</id>
    <published>2026-06-28T00:00:00Z</published>
    <updated>2026-06-28T00:00:00Z</updated>
    <summary>How to connect the Tierux MCP server to your AI coding agent and let it wire up your entire subscription stack in one prompt.</summary>
  </entry>
  <entry>
    <title>Server-side purchase verification: the definitive guide</title>
    <link href="https://tierux.com/blog/server-side-purchase-verification-guide" rel="alternate" type="text/html"/>
    <id>https://tierux.com/blog/server-side-purchase-verification-guide</id>
    <published>2026-06-26T00:00:00Z</published>
    <updated>2026-06-26T00:00:00Z</updated>
    <summary>Why client-side verification is advisory at best, how server-side verification actually works, and the common engineering pitfalls when building it yourself.</summary>
  </entry>
  <entry>
    <title>Migrating to Google Play Billing 7: what changed</title>
    <link href="https://tierux.com/blog/google-play-billing-migration-guide" rel="alternate" type="text/html"/>
    <id>https://tierux.com/blog/google-play-billing-migration-guide</id>
    <published>2026-06-24T00:00:00Z</published>
    <updated>2026-06-24T00:00:00Z</updated>
    <summary>The key differences in Billing Library 7, how to handle the new subscription lifecycle APIs, and what breaks when you migrate from Billing 5 or 6.</summary>
  </entry>
  <entry>
    <title>No revenue tax: how app store fees compound</title>
    <link href="https://tierux.com/blog/no-revenue-tax-app-store-fees" rel="alternate" type="text/html"/>
    <id>https://tierux.com/blog/no-revenue-tax-app-store-fees</id>
    <published>2026-06-22T00:00:00Z</published>
    <updated>2026-06-22T00:00:00Z</updated>
    <summary>Apple and Google take 15-30%. Revenue-share billing tools take another ~1%. Here is how these fees compound and why flat-fee billing infrastructure changes the math.</summary>
  </entry>
</feed>
