{"id":262896,"date":"2026-04-23T08:24:50","date_gmt":"2026-04-23T08:24:50","guid":{"rendered":"https:\/\/staging.zycus.com\/?p=262896"},"modified":"2026-05-04T08:30:11","modified_gmt":"2026-05-04T08:30:11","slug":"enterprise-procurement-ai-depth-meets-startup-speed","status":"publish","type":"post","link":"https:\/\/dev.zycus.com\/freshz\/blog\/ai-agents\/enterprise-procurement-ai-depth-meets-startup-speed","title":{"rendered":"Enterprise Depth, Startup Speed: Why the Agentic Procurement Race Has Already Been Won"},"content":{"rendered":"<h2>TL;DR<\/h2>\n<ul>\n<li>Enterprise procurement AI was framed as depth vs speed \u2014 it was a false choice. The trade-off CPOs thought they had to make never actually existed.<\/li>\n<li>AI-native platforms nailed intake, missed fulfillment. Great front door, not enough depth behind it.<\/li>\n<li>Enterprise suites had depth, but bolted AI on top. Real substrate, non-native agentic layer.<\/li>\n<li>Accumulated depth became the unfair advantage. Agentic AI needs governed data, deterministic workflows, and contextual specificity \u2014 things deep S2P suites already had.<\/li>\n<li>The winning architecture is three layers. Guided Intake + native Agentic Platform + deep S2P suite \u2014 the shape of Zycus&#8217;s Merlin Agentic Platform.<\/li>\n<li>Gartner, Forrester, IDC, and Hackett agree. Four independent lenses, one Leader.<br \/>\nThe race is already over. Decided by architecture years ago, not by 2026 demos.<\/li>\n<\/ul>\n<p><em>The trade-off everyone assumed was permanent turned out to be a category mistake. Here\u2019s what the depth-or-speed argument missed \u2014 and why the platforms that figured it out have already crossed the finish line.<br \/>\n<\/em><\/p>\n<p>For the, every CPO sitting through an agentic procurement RFP has faced a shortlist organised into two camps that seemed to demand opposite trade-offs.<\/p>\n<p>In one camp: AI-native platforms, often built in the last three to four years, designed from the ground up around conversational interfaces and agentic execution. Beautiful intake. Natural-language requests. Fast deployment. Demos that captured the imagination of business users who were tired of portals nobody wanted to use.<\/p>\n<p>In the other camp: <a href=\"https:\/\/dev.zycus.com\/freshz\/solution\/source-to-pay\">enterprise S2P suites<\/a>, accumulated over a generation of category-by-category refinement. Deep workflow rigour. Global compliance coverage. Mature integrations across the universe of ERPs and tax engines. Decades of edge-case handling that no startup had yet encountered.<\/p>\n<p>Both camps were making valid arguments. The conventional wisdom said the trade-off was structural \u2014 depth or speed, pick one. The two requirements seemed to demand opposite kinds of organizations: the patient enterprise builder and the fast-moving AI-native startup. No single vendor could be both.<\/p>\n<p>What the conventional wisdom missed is what this piece is about.<\/p>\n<p><strong>Read more:<\/strong> <a href=\"https:\/\/dev.zycus.com\/freshz\/blog\/source-to-pay\/large-medium-enterprise-procurement-strategies\">Strategies for Large and Medium Enterprises: Mastering Source-to-Pay Before It\u2019s Too Late<\/a><\/p>\n<h2>What Each Camp Got Right, and Where Each One Stopped<\/h2>\n<p>The AI-native camp was right about something the enterprise camp had been slow to admit. For too long, procurement software had been built for procurement teams rather than for the business users who actually needed to buy things. Forms that nobody filled out correctly. Portals that requestors avoided by emailing procurement directly. Approval flows that felt like punishment for trying to follow the process. The AI-native platforms identified the real user \u2014 the marketing manager who needs display stands, the engineer who needs lab supplies \u2014 and built for that user first. That was a genuine architectural insight, not a marketing one.<\/p>\n<p>Where this camp hit a ceiling was in the depth required to fulfil what intake had captured. A natural-language request for display stands is the easy part. Routing it through a global supplier ecosystem that respects forty jurisdictions of tax law, dozens of contract templates, supplier risk frameworks that pass a regulator\u2019s audit, and category-specific workflows refined across hundreds of customer deployments \u2014 that is the hard part. The hard part takes years to build, and most AI-native platforms did not have those years.<\/p>\n<p>The enterprise camp was right about something the AI-native camp couldn\u2019t easily replicate. The accumulated depth of an S2P suite \u2014 the workflow primitives, the contract logic, the supplier networks, the compliance engines, the data models that hold up across forty jurisdictions \u2014 is not a marketing claim. It is a multi-decade asset. It is the substrate that lets a procurement function actually operate at Fortune 500 scale.<\/p>\n<p><strong>Read more:<\/strong> <a href=\"https:\/\/dev.zycus.com\/freshz\/blog\/procurement-technology\/procurement-paradox-in-emerging-enterprises\">Flying the Plane While Fixing the Wings: The Procurement Paradox in Emerging Enterprises<\/a><\/p>\n<p>Where this camp hit its own ceiling was in how AI was added to the architecture. <span style=\"font-weight: normal !msorm;\"><strong>For most enterprise S2P suites, AI arrived as a layer on top of platforms designed in a pre-agent world<\/strong><\/span>. Conversational front doors bolted to monolithic backends. The depth was real. The AI was an attachment.<\/p>\n<p>Two camps. Two valid arguments. Two ceilings.<\/p>\n<p><em>Figure 1 \u00b7 The procurement AI shortlist as the market saw it \u2014 and the category most buyers didn\u2019t expect to find.<\/em><\/p>\n<p><img fetchpriority=\"high\" decoding=\"async\" class=\"wp-image-262898 aligncenter\" src=\"https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-1-Two-Camps-Matrix.webp\" alt=\"procurement AI - Two cramps\" width=\"769\" height=\"528\" srcset=\"https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-1-Two-Camps-Matrix.webp 2000w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-1-Two-Camps-Matrix-300x206.webp 300w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-1-Two-Camps-Matrix-1024x704.webp 1024w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-1-Two-Camps-Matrix-768x528.webp 768w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-1-Two-Camps-Matrix-1536x1056.webp 1536w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-1-Two-Camps-Matrix-150x103.webp 150w\" sizes=\"(max-width: 769px) 100vw, 769px\" \/><\/p>\n<h2>The Architectural Physics<\/h2>\n<p>The reason the depth-or-speed trade-off has been treated as unavoidable is that it almost is.<\/p>\n<p>Building a procurement platform with the depth a global enterprise demands takes years of category-by-category refinement. You learn how aerospace MRO is different from pharmaceutical raw materials, how compliance varies between jurisdictions, how supplier ecosystems shift over time. None of that can be speedrun. It has to be lived through with customers until the platform\u2019s logic carries the weight of the workflows underneath.<\/p>\n<p>Building an AI-native agentic platform requires a foundation designed for agents from the start \u2014 APIs deep enough to expose every workflow primitive, an integration backbone that lets agents communicate across systems, an orchestration layer that coordinates multiple agents in parallel, a unified data core so agents reason on the same facts the rest of the platform operates on. None of that retrofits cleanly onto architectures designed in a pre-agent era. You can wrap a chat interface around almost anything. You can\u2019t wrap an agentic execution layer around a monolith and expect it to behave.<\/p>\n<p><a href=\"https:\/\/www.mckinsey.com\/capabilities\/mckinsey-technology\/our-insights\/mckinsey-global-tech-agenda-2026\" target=\"_blank\" rel=\"nofollow noopener\">McKinsey\u2019s Global Tech Agenda 2026<\/a> surveyed more than 600 technology and business leaders and found a broad shift from episodic efficiency gains to organisational velocity \u2014 companies making teams more productive, streamlining workflows, and restructuring technology and operating models. Speed of execution has become the new moat. But what the same survey didn\u2019t say out loud is what every CIO had already figured out \u2014 that speed without depth is its own dead end. Pilots that demo well and never scale. Agents that work in isolation and break inside complex workflows.<\/p>\n<p>This is what made the depth-or-speed trade-off feel architectural rather than optional. It wasn\u2019t lazy thinking. It was an honest read of what the two requirements seemed to demand.<\/p>\n<p>So the question that hung over the market through 2024 and 2025 was: if the trade-off was as real as it looked, how did anyone escape it?<\/p>\n<h2>The Unfair Advantage Hiding in Plain Sight<\/h2>\n<p>The answer inverts a piece of conventional wisdom that had been taken as obvious.<\/p>\n<p>In most software categories, decades of accumulated depth is a disadvantage in the AI era. Older codebases. Monolithic architectures. Teams structured for sustaining maintenance rather than aggressive innovation. The dominant narrative has been that AI-native challengers should win because they are unburdened by legacy weight. In most categories, that narrative is correct.<\/p>\n<p>In procurement specifically, it isn\u2019t.<\/p>\n<p>Agentic AI in procurement requires three things that are unusually hard to build from scratch. It requires governed data \u2014 clean, unified, structured around the actual semantic shape of procurement transactions, not generic enterprise records. It requires deterministic workflows \u2014 the kind that hold up across compliance regimes and audit trails, not the probabilistic-best-effort logic that LLMs produce by default. And it requires contextual specificity \u2014 the accumulated knowledge of how a contract clause behaves differently in pharma than in aerospace, how a supplier risk score varies across jurisdictions, how an invoice exception in one country is a routine match in another.<\/p>\n<p>These three things \u2014 governed data, deterministic workflows, contextual specificity \u2014 are precisely what a deep S2P suite has been quietly accumulating for years. Not because anyone planned for the agentic era. Because procurement is the kind of domain where you cannot ship a product without those things.<\/p>\n<p>The accumulated depth that looked like legacy weight in 2022 turned out to be exactly the substrate that agentic AI needs to operate inside.<\/p>\n<p><em>Figure 2 \u00b7 The same three assets, two different readings. The architectural inversion that escaped the trade-off.<\/em><\/p>\n<p><img decoding=\"async\" class=\"wp-image-262899 aligncenter\" src=\"https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-3-Substrate-Inversion.webp\" alt=\"agentic ai in procurement\" width=\"788\" height=\"492\" srcset=\"https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-3-Substrate-Inversion.webp 2000w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-3-Substrate-Inversion-300x188.webp 300w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-3-Substrate-Inversion-1024x640.webp 1024w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-3-Substrate-Inversion-768x480.webp 768w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-3-Substrate-Inversion-1536x960.webp 1536w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-3-Substrate-Inversion-150x94.webp 150w\" sizes=\"(max-width: 788px) 100vw, 788px\" \/><\/p>\n<p>This is the inversion the market is still adjusting to. The platforms that combined enterprise depth with startup speed didn\u2019t escape the trade-off through clever engineering. They discovered that the depth was the unfair advantage all along \u2014 and the only architectural work left was to build a native agentic layer that could sit on top of it.<\/p>\n<h2>What that Combination Actually Looks Like<\/h2>\n<p>The architectural shape of enterprise depth and startup speed is specific and traceable.<\/p>\n<p>It is a three-layer stack. At the top, a guided intake layer \u2014 the conversational front door where any procurement request is captured in natural language, without forms and without training. In the middle, a native agentic platform \u2014 specialised agents for autonomous negotiation, agentic sourcing, supplier onboarding, and accounts payable, coordinated by an agent orchestration layer and connected through more than a thousand APIs, a Model Context Protocol server, and a tool library. At the foundation, a deep source-to-pay suite \u2014 built up over a generation of category-by-category refinement, compliance-grade workflows, and a unified data core that every agent reasons on.<\/p>\n<p>Zycus\u2019s Merlin Agentic Platform is the architectural exemplar of this pattern. The agentic layer was built natively for multi-agent execution \u2014 specialised agents orchestrated across the S2P backbone, not a chat UI bolted onto a pre-agent backend. It connects to the suite through <a href=\"https:\/\/dev.zycus.com\/freshz\/solution\/merlin-agentic-ai-platform\">1,121 APIs<\/a>, reasons on the unified Zycus Data Core, and operates across the full procurement lifecycle through the Merlin agent family: <a href=\"https:\/\/dev.zycus.com\/freshz\/solution\/intake-management\">Merlin Intake<\/a>, <a href=\"https:\/\/dev.zycus.com\/freshz\/solution\/merlin-ana\">ANA (Autonomous Negotiation Agent)<\/a>, <a href=\"https:\/\/dev.zycus.com\/freshz\/solution\/esourcing-software\">Merlin Agentic Sourcing<\/a>, <a href=\"https:\/\/dev.zycus.com\/freshz\/knowledge-hub\/whitepapers\/improve-ap-supplier-relationships-with-zycus-ap-smart-desk\">AP SmartDesk<\/a>, and the <a href=\"https:\/\/dev.zycus.com\/freshz\/solution\/supplier-management\">Autonomous Supplier Onboarding Agent<\/a>. The three-layer Intake-to-Outcomes architecture \u2014 Guided Intake, Agentic AI, and a deep S2P foundation \u2014 is the structural expression of depth-plus-speed in a single platform.<\/p>\n<p><em>Figure 3 \u00b7 The three-layer Intake-to-Outcomes architecture. Guided Intake at the top, a native Merlin Agentic Platform in the middle, and a deep S2P suite \u2014 with the Zycus Data Core as unified data spine \u2014 at the foundation.<\/em><\/p>\n<p><img decoding=\"async\" class=\"wp-image-262900 aligncenter\" src=\"https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-2-I2O-Architecture.webp\" alt=\"three-layer Intake-to-Outcomes architecture \" width=\"740\" height=\"523\" srcset=\"https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-2-I2O-Architecture.webp 2000w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-2-I2O-Architecture-300x212.webp 300w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-2-I2O-Architecture-1024x724.webp 1024w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-2-I2O-Architecture-768x543.webp 768w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-2-I2O-Architecture-1536x1087.webp 1536w, https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/04\/Race-Visual-2-I2O-Architecture-150x106.webp 150w\" sizes=\"(max-width: 740px) 100vw, 740px\" \/><\/p>\n<p>The clearest evidence that something architectural happened is that the market\u2019s independent referees noticed it independently. Over the last eighteen months, three major analyst firms \u2014 Gartner, Forrester, and IDC \u2014 have each placed Zycus in their leader positions, and The Hackett Group has partnered with Zycus on the definitive benchmark study of agentic AI adoption in procurement.<\/p>\n<p>The <a href=\"https:\/\/dev.zycus.com\/freshz\/press-releases\/zycus-named-a-leader-in-the-2026-gartner-magic-quadrant-for-source-to-pay-suites\">2026 Gartner\u00ae Magic Quadrant\u2122 for Source-to-Pay Suites<\/a> named Zycus a Leader. <a href=\"https:\/\/dev.zycus.com\/freshz\/press-releases\/zycus-named-leader-in-forrester-wave-supplier-value-management-svm-platforms\">The Forrester Wave\u2122: Supplier Value Management Platforms, Q3 2024<\/a> recognised Zycus as a Leader. The <a href=\"https:\/\/dev.zycus.com\/freshz\/press-releases\/zycus-idc-leader-ai-source-to-pay-2025\">IDC MarketScape: Worldwide AI-Enabled Source-to-Pay 2025 Vendor Assessment<\/a> named Zycus a Leader. And <a href=\"https:\/\/dev.zycus.com\/freshz\/press-releases\/hackett-group-procurement-benchmark-2026-agentic-ai\">The Hackett Group and Zycus have collaborated<\/a> on landmark research into agentic AI in procurement, including the 2026 Agentic AI in Procurement Adoption Index built on 250+ global CPO surveys.<\/p>\n<p>These firms do not coordinate. They use different criteria. They reached the same conclusion about this one because the same conclusion was visible to anyone with a serious measurement framework. Four independent lenses, one answer.<\/p>\n<h2>The Race Already Run<\/h2>\n<p>The race the procurement industry thought it was running \u2014 speed versus depth, startups versus suites, AI-native versus enterprise-grade \u2014 was the wrong race. The real race was simpler. It was about which platforms recognised that depth was the unfair advantage, and which platforms then did the architectural work to combine that depth with a native agentic layer designed for the era that had just arrived.<\/p>\n<p>That race wasn\u2019t decided by sales demos in 2026. It was decided by architectural choices made \u2014 or not made \u2014 in the years before most buyers started shopping. By the time the public conversation about agentic procurement reached its current pitch, the platforms that combined enterprise depth with startup speed had already crossed the line.<\/p>\n<p><strong>Explore Zycus&#8217; <a href=\"https:\/\/dev.zycus.com\/freshz\/solution\/large-enterprise\">Procurement Software for Large Enterprises<\/a><\/strong><\/p>\n<p>The CPO sitting through an RFP in 2026 doesn\u2019t have to choose between the two camps anymore. The buyer who insists on choosing between them is solving yesterday\u2019s problem.<\/p>\n<p>The race has already been run. The question now is which platforms the buyer recognises as having finished it.<\/p>\n<p><strong>Related Reads:<\/strong><\/p>\n<ol>\n<li><a href=\"https:\/\/dev.zycus.com\/freshz\/blog\/ai-agents\/agentic-ai-in-source-to-pay-s2p\">Why Agentic AI Is the Future of Source-to-Pay Automation by 2026<\/a><\/li>\n<li><a href=\"https:\/\/dev.zycus.com\/freshz\/blog\/autonomous-negotiation-agents\/agentic-ai-in-sourcing-whats-real-vs-hype\">Agentic AI in Sourcing: What\u2019s Real vs Hype<\/a><\/li>\n<li style=\"text-align: left;\"><a href=\"https:\/\/dev.zycus.com\/freshz\/knowledge-hub\/whitepapers\/unlocking-deep-value-the-impact-of-agentic-ai-on-source-to-pay\">Whitepaper: Unlocking Deep Value: The Impact of Agentic AI on Source-to-Pay<\/a><\/li>\n<li><a href=\"https:\/\/dev.zycus.com\/freshz\/knowledge-hub\/whitepapers\/agentic-ai-in-procurement\">Whitepaper: Beyond GenAI: The Dawn of Agentic AI<\/a><\/li>\n<li><a href=\"https:\/\/dev.zycus.com\/freshz\/knowledge-hub\/magazine\/beyond-source-to-pay-agentic-ai-driven-procurement\">Magazine: Intake to Outcomes (I2O) with Agentic AI-powered Procurement<\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>TL;DR Enterprise procurement AI was framed as depth vs speed \u2014 it was a false choice. The trade-off CPOs thought they had to make never actually existed. AI-native platforms nailed intake, missed fulfillment. Great front door, not enough depth behind it. Enterprise suites had depth, but bolted AI on top. Real substrate, non-native agentic layer. [&hellip;]<\/p>\n","protected":false},"author":201,"featured_media":262897,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"default","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[2456],"tags":[],"ppma_author":[2712],"class_list":["post-262896","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agentic-ai"],"acf":[],"authors":[{"term_id":2712,"user_id":201,"is_guest":0,"slug":"uday-jain","display_name":"Uday Jain","avatar_url":{"url":"https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/05\/Profile-photo-r23f1c03.webp","url2x":"https:\/\/dev.zycus.com\/freshz\/wp-content\/uploads\/2026\/05\/Profile-photo-r23f1c03.webp"},"author_category":"0","last_name":"Jain","first_name":"Uday","job_title":"","user_url":"","description":"Uday in the business of making procurement leaders read past the first line. Content and product marketer at Zycus, turning product complexity into something worth their time. Demand gen is where I learned the craft from the ground up. Every headline earning the click, every paragraph earning the next, every word pulling its weight. If they bookmark it, I've done my job. If they share it, I've done it well."}],"_links":{"self":[{"href":"https:\/\/dev.zycus.com\/freshz\/wp-json\/wp\/v2\/posts\/262896","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.zycus.com\/freshz\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.zycus.com\/freshz\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.zycus.com\/freshz\/wp-json\/wp\/v2\/users\/201"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.zycus.com\/freshz\/wp-json\/wp\/v2\/comments?post=262896"}],"version-history":[{"count":0,"href":"https:\/\/dev.zycus.com\/freshz\/wp-json\/wp\/v2\/posts\/262896\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dev.zycus.com\/freshz\/wp-json\/wp\/v2\/media\/262897"}],"wp:attachment":[{"href":"https:\/\/dev.zycus.com\/freshz\/wp-json\/wp\/v2\/media?parent=262896"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.zycus.com\/freshz\/wp-json\/wp\/v2\/categories?post=262896"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.zycus.com\/freshz\/wp-json\/wp\/v2\/tags?post=262896"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/dev.zycus.com\/freshz\/wp-json\/wp\/v2\/ppma_author?post=262896"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}