<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>API on Yūhi (夕陽)</title>
    <link>https://yuhi.me/tags/api/</link>
    <description>Recent content in API on Yūhi (夕陽)</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 20 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://yuhi.me/tags/api/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Joy Reads Your Health Data: A Technical Look at the openLife API</title>
      <link>https://yuhi.me/blog/2026-02-20-joy-api-deep-dive/</link>
      <pubDate>Fri, 20 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://yuhi.me/blog/2026-02-20-joy-api-deep-dive/</guid>
      <description>&lt;p&gt;In our &lt;a href=&#34;https://yuhi.me/blog/2026-02-20-openlife-ecosystem/&#34;&gt;first openLife post&lt;/a&gt;, we introduced the ecosystem and its three core components. Today, we&amp;rsquo;re going under the hood to see how Joy actually reads and uses your health data.&lt;/p&gt;&#xA;&lt;p&gt;If you&amp;rsquo;re curious about how AI agents can interact with personal health metrics — or if you&amp;rsquo;re building something similar — this one&amp;rsquo;s for you.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-api-first-philosophy&#34;&gt;The API-First Philosophy&lt;/h2&gt;&#xA;&lt;p&gt;Before we get into code, it&amp;rsquo;s worth understanding the design philosophy behind openLife. Many health dashboards treat APIs as an afterthought — they build a UI first and bolt on data endpoints later. openLife took the opposite approach:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
