{"id":113,"date":"2026-03-19T06:30:34","date_gmt":"2026-03-19T06:30:34","guid":{"rendered":"https:\/\/tokita.online\/?p=113"},"modified":"2026-05-04T17:04:49","modified_gmt":"2026-05-04T17:04:49","slug":"llm-wrappers-what-actually-matters","status":"publish","type":"post","link":"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/","title":{"rendered":"Most AI Tools Are Just LLM Wrappers. Here’s What Actually Matters."},"content":{"rendered":"

In 2025, over $200 billion poured into AI startups<\/a>, and a staggering share went to the application layer.<\/strong> The product? Take an LLM API. Add a text box. Maybe some prompt templates. Charge $30\/month. Call it “AI-powered.”<\/p>\n

Not mad at the hustle.<\/strong> But if your entire product disappears the moment ChatGPT adds your feature for free, you don’t have a product. You have a timing play.<\/p>\n

\n

A Practitioner’s AI Tool Evaluation Framework<\/h2>\n

Before you spend, score.<\/strong> This is the framework I use to evaluate any AI tool, wrapper or otherwise:<\/p>\n\n\n\n\n\n\n\n\n\n
Criteria<\/th>\nQuestion to Ask<\/th>\nRed Flag<\/th>\n<\/tr>\n<\/thead>\n
Replicability<\/strong><\/td>\nCan I get the same output by pasting the input into ChatGPT?<\/td>\nYes = thin wrapper<\/td>\n<\/tr>\n
Connectors<\/strong><\/td>\nDoes it integrate with my actual systems (CRM, ticketing, deployment)?<\/td>\nText-in\/text-out only<\/td>\n<\/tr>\n
Memory<\/strong><\/td>\nDoes it learn from previous sessions, or start fresh every time?<\/td>\nNo persistence<\/td>\n<\/tr>\n
Methodology<\/strong><\/td>\nDoes it capture learnings and improve, or just run prompts?<\/td>\nNo feedback loop<\/td>\n<\/tr>\n
Survivability<\/strong><\/td>\nIf the underlying model adds this feature natively, does the tool still matter?<\/td>\nEntire value prop disappears<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Score 0\u20132 on each.<\/strong> Below 5 out of 10? You’re renting a feature, not buying a tool. Above 7? Probably worth the spend.<\/p>\n

\n

The Wrapper Test<\/h2>\n

One question tells you everything:<\/strong><\/p>\n

\n

Can you replicate the output by pasting the same input into ChatGPT or Claude?<\/p>\n<\/blockquote>\n

If yes<\/strong>, it’s a wrapper. You’re paying for UI and convenience, not intelligence.<\/p>\n

If no<\/strong>, because it’s pulling from multiple data sources, applying domain logic, or integrating with real systems, it might be something real.<\/p>\n

Most fail the test.<\/strong><\/p>\n

\n

Thin vs. Thick<\/h2>\n

Not all wrappers are equal.<\/strong> The market is splitting fast:<\/p>\n\n\n\n\n\n\n\n\n
<\/th>\nThin Wrapper<\/th>\nThick Wrapper<\/th>\n<\/tr>\n<\/thead>\n
What it does<\/strong><\/td>\nUI + API call + system prompt<\/td>\nReal integrations, domain logic, data pipelines<\/td>\n<\/tr>\n
Defensibility<\/strong><\/td>\nNone: one platform update kills it<\/td>\nHigh: value is in the connectors<\/td>\n<\/tr>\n
Example<\/strong><\/td>\n“AI email writer” (GPT call with a system prompt)<\/td>\nCursor (reads your codebase, understands project context)<\/td>\n<\/tr>\n
Survival odds<\/strong><\/td>\nLow<\/td>\nDecent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The graveyard of 2025\u20132026<\/strong> is littered with thin wrappers that a platform update made irrelevant overnight.<\/p>\n

\n

What Actually Matters<\/h2>\n

Strip away the wrapper.<\/strong> Where does the real value live?<\/p>\n

1. Connectors<\/h3>\n

The ability to talk to real systems<\/strong>. Salesforce, Jira, databases, email, file storage, APIs. This is where 80% of the actual work lives.<\/p>\n

Getting an AI to generate text is trivial.<\/strong> Getting it to read your CRM records, cross-reference tickets, update a database, and notify Slack, that’s integration work. That’s hard. That’s valuable.<\/p>\n

Most wrappers don’t touch this.<\/strong> They live in the text-in, text-out world.<\/p>\n

2. Captured Domain Expertise<\/h3>\n

An AI that’s been learning your industry’s quirks for months<\/strong> is worth more than a fresh GPT-5 instance with a clever prompt.<\/p>\n\n\n\n\n\n\n\n\n
<\/th>\nFresh AI + Great Prompt<\/th>\nAI + 6 Months of Learnings<\/th>\n<\/tr>\n<\/thead>\n
Platform quirks<\/strong><\/td>\nDiscovers them painfully<\/td>\nAlready knows them<\/td>\n<\/tr>\n
Common mistakes<\/strong><\/td>\nMakes them all<\/td>\nHas guardrails for each<\/td>\n<\/tr>\n
Your terminology<\/strong><\/td>\nConstant correction needed<\/td>\nUses it naturally<\/td>\n<\/tr>\n
Edge cases<\/strong><\/td>\nSurprised every time<\/td>\nDocumented patterns<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The knowledge compounds.<\/strong> Every session, every bug fix, every “oh, that’s how this actually works” gets captured and fed back.<\/p>\n

No wrapper captures this.<\/strong> They start fresh every time. This is why context engineering<\/a>, persistent memory, retrieval layers, enforcement gates, matters more than the tool you’re using.<\/p>\n

3. Methodology<\/h3>\n

How you approach problems with AI<\/strong> matters more than which model you use.<\/p>\n

The wrapper approach:<\/strong> open tool \u2192 type request \u2192 get output \u2192 hope it’s right.<\/p>\n

The practitioner approach:<\/strong><\/p>\n

    \n
  1. Small test<\/strong>, constrained input, see what happens<\/li>\n
  2. Evaluate<\/strong>, what worked? What broke?<\/li>\n
  3. Capture<\/strong>, document the learning<\/li>\n
  4. Adjust<\/strong>, update the approach<\/li>\n
  5. Repeat<\/strong><\/li>\n<\/ol>\n

    The tool is 10%. The methodology is 90%.<\/strong><\/p>\n

    \n

    The “Just Build It” Case<\/h2>\n

    Here’s the uncomfortable truth.<\/strong> Building your own system, even ugly, even scrappy, gives you something no wrapper provides: understanding.<\/strong><\/p>\n

    You know why it works.<\/strong> Why it breaks. How to fix it. When the model changes (and it will), you swap the engine. The connectors, the learnings, the guardrails, those persist. They’re yours.<\/p>\n

    Cost at scale:<\/h3>\n\n\n\n\n\n\n\n
    <\/th>\nWrapper Stack<\/th>\nCustom (Direct API)<\/th>\n<\/tr>\n<\/thead>\n
    Month 1<\/strong><\/td>\n$150\/seat: fast setup<\/td>\n$500 dev time: slower start<\/td>\n<\/tr>\n
    Month 6<\/strong><\/td>\n$150\/seat: same capabilities<\/td>\n$50\/month API: growing capabilities<\/td>\n<\/tr>\n
    Year 1 (5 seats)<\/strong><\/td>\n$9,000<\/td>\n~$3,100 + compound knowledge<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Custom costs less AND gets smarter.<\/strong> The wrapper costs the same and stays the same. And when you go custom, you need to think about what autonomous agents actually cost in production<\/a>, not just the sticker price.<\/p>\n

    The Philippines advantage:<\/strong> smaller teams with direct API access can outperform larger orgs paying for wrapper stacks. When you can’t afford $150\/seat for 6 different AI tools, you build one system that does what you need. That constraint produces better architecture.<\/p>\n

    \n

    When Wrappers DO Make Sense<\/h2>\n

    Fair is fair:<\/strong><\/p>\n

      \n
    • Speed to market<\/strong>, need something running tomorrow without engineering capacity? Wrapper gets you there.<\/li>\n
    • Thick wrappers with real integrations<\/strong>. Cursor, Harvey, Perplexity add genuine value beyond the API call.<\/li>\n
    • Exploration phase<\/strong>, trying 5 wrappers to understand the capability space before building your own is smart R&D.<\/li>\n<\/ul>\n

      The key question:<\/strong><\/p>\n

      \n

      Are you buying a tool or renting a feature?<\/p>\n<\/blockquote>\n

      If the value prop is “we make it easy to talk to an LLM,”<\/strong> that feature is getting commoditized in real time. Every model provider is making their native interface better, faster, cheaper.<\/p>\n

      \n

      What to Build Instead<\/h2>\n

      Ready to go beyond wrappers?<\/strong> Start here:<\/p>\n

      1. Map your connectors.<\/strong> What systems does your AI need to talk to? Build those integrations first. Hardest part. Most valuable.<\/p>\n

      2. Capture everything.<\/strong> Every platform quirk. Every failed approach. Every successful pattern. Your AI should learn from your organization’s experience, not start fresh every session.<\/p>\n

      3. Own your methodology.<\/strong> Document how you approach problems with AI. Small tests \u2192 captured learnings \u2192 iteration. More valuable than any tool you can buy.<\/p>\n

      4. Accept ugly.<\/strong> The most effective AI systems I’ve built are not pretty. Config files, markdown documents, scripts. They look like plumbing. They work like machines.<\/p>\n

      \n

      Bottom Line<\/h2>\n

      The moat isn’t the model.<\/strong> It never was.<\/p>\n

      It’s the connectors<\/strong> that talk to your stack. The domain expertise captured over months. The methodology that turns every failure into a lesson.<\/p>\n

      None of that lives in a wrapper.<\/p>\n","protected":false},"excerpt":{"rendered":"

      In 2025, over $200 billion poured into AI startups, and a staggering share went to the application layer. The product? Take an LLM API. Add a text box. Maybe some prompt templates. Charge $30\/month. Call it “AI-powered.” Not mad at the hustle. But if your entire product disappears the moment ChatGPT adds your feature for free, you don’t have a product. You have a timing play. A Practitioner’s AI Tool Evaluation Framework Before you spend, score. This is the framework I use to evaluate any AI tool, wrapper or otherwise: Criteria Question to Ask Red Flag Replicability Can I get the same output by pasting the input into ChatGPT? Yes = thin wrapper Connectors Does it integrate with my actual systems (CRM, ticketing, deployment)? Text-in\/text-out only Memory Does it learn from previous sessions, or start fresh every time? No persistence Methodology Does it capture learnings and improve, or just run prompts? No feedback loop Survivability If the underlying model adds this feature natively, does the tool still matter? Entire value prop disappears Score 0\u20132 on each. Below 5 out of 10? You’re renting a feature, not buying a tool. Above 7? Probably worth the spend. The Wrapper Test One question tells you everything: Can you replicate the output by pasting the same input into ChatGPT or Claude? If yes, it’s a wrapper. You’re paying for UI and convenience, not intelligence. If no, because it’s pulling from multiple data sources, applying domain logic, or integrating with real systems, it might be something real. Most fail the test. Thin vs. Thick Not all wrappers are equal. The market is splitting fast: Thin Wrapper Thick Wrapper What it does UI + API call + system prompt Real integrations, domain logic, data pipelines Defensibility None: one platform update kills it High: value is in the connectors Example “AI email writer” (GPT call with a system prompt) Cursor (reads your codebase, understands project context) Survival odds Low Decent The graveyard of 2025\u20132026 is littered with thin wrappers that a platform update made irrelevant overnight. What Actually Matters Strip away the wrapper. Where does the real value live? 1. Connectors The ability to talk to real systems. Salesforce, Jira, databases, email, file storage, APIs. This is where 80% of the actual work lives. Getting an AI to generate text is trivial. Getting it to read your CRM records, cross-reference tickets, update a database, and notify Slack, that’s integration work. That’s hard. That’s valuable. Most wrappers don’t touch this. They live in the text-in, text-out world. 2. Captured Domain Expertise An AI that’s been learning your industry’s quirks for months is worth more than a fresh GPT-5 instance with a clever prompt. Fresh AI + Great Prompt AI + 6 Months of Learnings Platform quirks Discovers them painfully Already knows them Common mistakes Makes them all Has guardrails for each Your terminology Constant correction needed Uses it naturally Edge cases Surprised every time Documented patterns The knowledge compounds. Every session, every bug fix, every “oh, that’s how this actually works” gets captured and fed back. No wrapper captures this. They start fresh every time. This is why context engineering, persistent memory, retrieval layers, enforcement gates, matters more than the tool you’re using. 3. Methodology How you approach problems with AI matters more than which model you use. The wrapper approach: open tool \u2192 type request \u2192 get output \u2192 hope it’s right. The practitioner approach: Small test, constrained input, see what happens Evaluate, what worked? What broke? Capture, document the learning Adjust, update the approach Repeat The tool is 10%. The methodology is 90%. The “Just Build It” Case Here’s the uncomfortable truth. Building your own system, even ugly, even scrappy, gives you something no wrapper provides: understanding. You know why it works. Why it breaks. How to fix it. When the model changes (and it will), you swap the engine. The connectors, the learnings, the guardrails, those persist. They’re yours. Cost at scale: Wrapper Stack Custom (Direct API) Month 1 $150\/seat: fast setup $500 dev time: slower start Month 6 $150\/seat: same capabilities $50\/month API: growing capabilities Year 1 (5 seats) $9,000 ~$3,100 + compound knowledge Custom costs less AND gets smarter. The wrapper costs the same and stays the same. And when you go custom, you need to think about what autonomous agents actually cost in production, not just the sticker price. The Philippines advantage: smaller teams with direct API access can outperform larger orgs paying for wrapper stacks. When you can’t afford $150\/seat for 6 different AI tools, you build one system that does what you need. That constraint produces better architecture. When Wrappers DO Make Sense Fair is fair: Speed to market, need something running tomorrow without engineering capacity? Wrapper gets you there. Thick wrappers with real integrations. Cursor, Harvey, Perplexity add genuine value beyond the API call. Exploration phase, trying 5 wrappers to understand the capability space before building your own is smart R&D. The key question: Are you buying a tool or renting a feature? If the value prop is “we make it easy to talk to an LLM,” that feature is getting commoditized in real time. Every model provider is making their native interface better, faster, cheaper. What to Build Instead Ready to go beyond wrappers? Start here: 1. Map your connectors. What systems does your AI need to talk to? Build those integrations first. Hardest part. Most valuable. 2. Capture everything. Every platform quirk. Every failed approach. Every successful pattern. Your AI should learn from your organization’s experience, not start fresh every session. 3. Own your methodology. Document how you approach problems with AI. Small tests \u2192 captured learnings \u2192 iteration. More valuable than any tool you can buy. 4. Accept ugly. The most effective AI systems I’ve built are not pretty. Config files, markdown documents, scripts. They look like plumbing. They work like machines. Bottom Line The moat isn’t the model. It never was. It’s the connectors that talk to your stack. The domain expertise captured over<\/p>\n","protected":false},"author":1,"featured_media":116,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-113","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"yoast_head":"\nMost AI Tools Are Just LLM Wrappers. Here's What Actually Matters.<\/title>\n<meta name=\"description\" content=\"How to evaluate AI tools beyond the wrapper. A practitioner framework: connectors, domain expertise, and methodology matter more than the UI.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Most AI Tools Are Just LLM Wrappers. Here's What Actually Matters.\" \/>\n<meta property=\"og:description\" content=\"How to evaluate AI tools beyond the wrapper. A practitioner framework: connectors, domain expertise, and methodology matter more than the UI.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/\" \/>\n<meta property=\"og:site_name\" content=\"Tom Tokita\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-19T06:30:34+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-04T17:04:49+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/tokita.online\/wp-content\/uploads\/2026\/03\/featured-llm-wrappers.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"1024\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Tom Tokita\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Tom Tokita\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Most AI Tools Are Just LLM Wrappers. Here's What Actually Matters.","description":"How to evaluate AI tools beyond the wrapper. A practitioner framework: connectors, domain expertise, and methodology matter more than the UI.","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:\/\/tokita.online\/llm-wrappers-what-actually-matters\/","og_locale":"en_US","og_type":"article","og_title":"Most AI Tools Are Just LLM Wrappers. Here's What Actually Matters.","og_description":"How to evaluate AI tools beyond the wrapper. A practitioner framework: connectors, domain expertise, and methodology matter more than the UI.","og_url":"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/","og_site_name":"Tom Tokita","article_published_time":"2026-03-19T06:30:34+00:00","article_modified_time":"2026-05-04T17:04:49+00:00","og_image":[{"width":1024,"height":1024,"url":"https:\/\/tokita.online\/wp-content\/uploads\/2026\/03\/featured-llm-wrappers.jpg","type":"image\/jpeg"}],"author":"Tom Tokita","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Tom Tokita","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/#article","isPartOf":{"@id":"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/"},"author":{"name":"Tom Tokita","@id":"https:\/\/tokita.online\/#\/schema\/person\/b420ed074b20ee6cb7a1f0f11c8dacdd"},"headline":"Most AI Tools Are Just LLM Wrappers. Here’s What Actually Matters.","datePublished":"2026-03-19T06:30:34+00:00","dateModified":"2026-05-04T17:04:49+00:00","mainEntityOfPage":{"@id":"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/"},"wordCount":1014,"publisher":{"@id":"https:\/\/tokita.online\/#organization"},"image":{"@id":"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/#primaryimage"},"thumbnailUrl":"https:\/\/tokita.online\/wp-content\/uploads\/2026\/03\/featured-llm-wrappers.jpg","articleSection":["Blog"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/","url":"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/","name":"Most AI Tools Are Just LLM Wrappers. Here's What Actually Matters.","isPartOf":{"@id":"https:\/\/tokita.online\/#website"},"primaryImageOfPage":{"@id":"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/#primaryimage"},"image":{"@id":"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/#primaryimage"},"thumbnailUrl":"https:\/\/tokita.online\/wp-content\/uploads\/2026\/03\/featured-llm-wrappers.jpg","datePublished":"2026-03-19T06:30:34+00:00","dateModified":"2026-05-04T17:04:49+00:00","description":"How to evaluate AI tools beyond the wrapper. A practitioner framework: connectors, domain expertise, and methodology matter more than the UI.","breadcrumb":{"@id":"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/#primaryimage","url":"https:\/\/tokita.online\/wp-content\/uploads\/2026\/03\/featured-llm-wrappers.jpg","contentUrl":"https:\/\/tokita.online\/wp-content\/uploads\/2026\/03\/featured-llm-wrappers.jpg","width":1024,"height":1024},{"@type":"BreadcrumbList","@id":"https:\/\/tokita.online\/llm-wrappers-what-actually-matters\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/tokita.online\/"},{"@type":"ListItem","position":2,"name":"Most AI Tools Are Just LLM Wrappers. Here’s What Actually Matters."}]},{"@type":"WebSite","@id":"https:\/\/tokita.online\/#website","url":"https:\/\/tokita.online\/","name":"Tom Tokita","description":"","publisher":{"@id":"https:\/\/tokita.online\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/tokita.online\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/tokita.online\/#organization","name":"Tom Tokita","url":"https:\/\/tokita.online\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/tokita.online\/#\/schema\/logo\/image\/","url":"https:\/\/tokita.online\/wp-content\/uploads\/2026\/03\/tokita-logo-clear-cropped.webp","contentUrl":"https:\/\/tokita.online\/wp-content\/uploads\/2026\/03\/tokita-logo-clear-cropped.webp","width":474,"height":151,"caption":"Tom Tokita"},"image":{"@id":"https:\/\/tokita.online\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/tokita.online\/#\/schema\/person\/b420ed074b20ee6cb7a1f0f11c8dacdd","name":"Tom Tokita","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/1be5e8ad1bd8baf1b5103aa27f1190be4ad3ede9953719e4c3540813988094aa?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/1be5e8ad1bd8baf1b5103aa27f1190be4ad3ede9953719e4c3540813988094aa?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/1be5e8ad1bd8baf1b5103aa27f1190be4ad3ede9953719e4c3540813988094aa?s=96&d=mm&r=g","caption":"Tom Tokita"},"sameAs":["https:\/\/tokita.online"],"url":"https:\/\/tokita.online\/author\/t-tokitajr\/"}]}},"_links":{"self":[{"href":"https:\/\/tokita.online\/?rest_route=\/wp\/v2\/posts\/113","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tokita.online\/?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tokita.online\/?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tokita.online\/?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/tokita.online\/?rest_route=%2Fwp%2Fv2%2Fcomments&post=113"}],"version-history":[{"count":5,"href":"https:\/\/tokita.online\/?rest_route=\/wp\/v2\/posts\/113\/revisions"}],"predecessor-version":[{"id":200,"href":"https:\/\/tokita.online\/?rest_route=\/wp\/v2\/posts\/113\/revisions\/200"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tokita.online\/?rest_route=\/wp\/v2\/media\/116"}],"wp:attachment":[{"href":"https:\/\/tokita.online\/?rest_route=%2Fwp%2Fv2%2Fmedia&parent=113"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tokita.online\/?rest_route=%2Fwp%2Fv2%2Fcategories&post=113"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tokita.online\/?rest_route=%2Fwp%2Fv2%2Ftags&post=113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}