{"id":11724,"date":"2026-11-03T12:30:00","date_gmt":"2026-11-03T12:30:00","guid":{"rendered":"https:\/\/www.cotocus.com\/blog\/?p=11724"},"modified":"2026-11-03T12:30:00","modified_gmt":"2026-11-03T12:30:00","slug":"case-study-verifying-local-partners","status":"publish","type":"post","link":"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/","title":{"rendered":"Case Study: A Team That Learned to Verify Local Partners"},"content":{"rendered":"

Every name in this story is invented; the pattern behind it is anything but. We have assembled it from recurring situations in consulting engagements precisely because it shows, step by step, how a capable engineering organisation can be terrible at verifying local partners \u2014 and how quickly that changes once someone treats trust as a system rather than a feeling. If your firm engages freelance specialists, regional installers or small local vendors, you will recognise more of this than is comfortable.<\/p>\n

The setup: a rollout that needed strangers<\/h2>\n

Call the company Verdalia \u2014 a 140-person logistics-software firm with its engineering hub in Pune. In early 2025, Verdalia won a contract to deploy warehouse tracking hardware and edge software across eleven Indian cities in five months. The core platform was solid; the constraint was hands. Each city needed a local integrator for racking, cabling and site commissioning, plus a freelance engineer for on-site acceptance testing. Twenty-two independent providers, none of whom anyone at Verdalia had met.<\/p>\n

Head of delivery Nisha Rao did what most delivery heads do: she collected recommendations from colleagues, skimmed portfolios, held video calls, and picked whoever sounded competent and available. The team’s own retrospective later described the method in three words: “vibes at scale”.<\/p>\n

The incident: three cities, three failure modes<\/h2>\n

By month two the evidence was in, and it was ugly. In Indore, the integrator who signed the agreement subcontracted the work to an unrelated crew; the person whose credentials Nisha had checked never set foot on site. In Coimbatore, the freelance engineer’s references turned out to be two friends and a cousin \u2014 his only completed commissioning job had been a fraction of the claimed scope. In Lucknow, a fifty-percent advance went to a firm whose registration, it emerged, had lapsed years earlier; when the work stalled there was no entity to hold to the contract.<\/p>\n

Total damage: six weeks of schedule, a contractual penalty, and roughly the cost of a senior hire in wasted advances. The post-incident review made the key observation: all three failures were detectable before engagement, with information that was free. Nobody had looked.<\/p>\n

The search for a model: why the fix came from tourism<\/h2>\n

Verdalia’s engineers wanted a framework, and the analytical instinct was to look at how other industries verify independent, geographically scattered providers at scale. The sharpest example came from an unexpected quarter. One of the platform engineers, planning a family trip, had been using the trust model HolidayLandmark applies to local travel<\/a> \u2014 a marketplace matching travellers to local guides, homestay operators, cooking hosts and drivers in India and several Asian countries \u2014 and realised it was solving Verdalia’s exact problem, stranger-to-stranger, every day.<\/p>\n

The mechanics mapped almost one to one. The platform verified her chosen trek organizer’s email and mobile, sighted an identity document, checked the operating business’s registration, and held the profile back until a reviewer cleared it \u2014 four confirmations where Verdalia had relied on one video call. Guest feedback was limited to travellers whose bookings had actually concluded, so testimonials were tied to delivered experiences rather than goodwill \u2014 where Verdalia had accepted reference lists it never dialled. A booking there began as dated terms: she submitted her travel window, awaited acceptance, and only then did phone numbers change hands \u2014 where Verdalia’s scopes had lived in calls and chat threads. Even the money matched: the traveller pays the organizer without the platform intermediating during its initial rollout, which works because the screening happens first \u2014 where Verdalia had wired advances before verifying anything.<\/p>\n

The rebuild: Verdalia’s partner-verification pipeline<\/h2>\n

Nisha’s team rebuilt their onboarding as a pipeline with gates \u2014 deliberately mirroring deployment practice, because the analogy kept everyone honest. The evidence-first mindset was already in the firm’s culture for tooling decisions, where they had long argued that claims need reviews, comparisons and verifiable evidence behind them<\/a>; the shift was applying the same standard to people.<\/p>\n

    \n
  1. Gate one \u2014 identity and entity.<\/strong> Legal name versus ID, ID versus payee account, firm versus live registration record, person versus public professional footprint. Time cost: under an hour per provider. This gate alone would have caught Lucknow.<\/li>\n
  2. Gate two \u2014 completed-work evidence.<\/strong> Minimum two prior deliveries of comparable scope, each confirmed by contacting the actual client or inspecting the running installation. Friends-and-family references scored zero. This gate would have caught Coimbatore.<\/li>\n
  3. Gate three \u2014 written request and named personnel.<\/strong> Scope, milestones, acceptance criteria and the names of the individuals performing the work, accepted in writing before any private-channel coordination. Substitution of personnel required written consent. This gate would have caught Indore.<\/li>\n
  4. Gate four \u2014 staged direct payment.<\/strong> Advances capped and tied to the first verifiable milestone; balance against acceptance tests; final tranche after documentation handover.<\/li>\n<\/ol>\n

    The results, measured<\/h2>\n

    Verdalia ran the remaining eight cities through the pipeline, then the next year’s engagements. The numbers their delivery dashboard showed after fourteen months make the case better than any argument. Provider-caused schedule slippage fell from the dominant delay category to statistical noise. Advance write-offs went to zero. Dispute resolution time collapsed, because every disagreement was settled against a written, accepted scope. Candidate drop-off during screening ran around a third \u2014 and exit conversations suggested most of those were drop-offs Verdalia wanted. Meanwhile the vetted bench became an asset: by the second rollout, six of the original providers were repeat partners, cleared through the gates once and re-engaged in days, supporting the firm’s broader push toward disciplined, stepwise use of outside operations expertise<\/a> instead of ad-hoc hiring.<\/p>\n

    One result surprised the sceptics. Quality of work rose, not just reliability of engagement. The screening had selected for professionals who keep records, confirm scope and welcome inspection \u2014 and those habits correlate tightly with how people cable a rack or run an acceptance test. Verification, it turned out, was not a filter in front of quality; it was a predictor of it.<\/p>\n

    The internal debate: friction versus speed<\/h2>\n

    The pipeline did not sail through unopposed, and the objections deserve a fair hearing because they will surface in any organisation that tries this. The sales team argued the gates would slow city launches; delivery data from the second rollout showed median onboarding time of four working days per provider, most of it running in parallel with site surveys that had to happen anyway. Finance questioned the cost of staff hours spent verifying; the quarter’s write-off ledger answered that one without commentary. The most serious challenge came from an engineering lead who pointed out that gates can rot into theatre \u2014 boxes ticked, nothing checked. Nisha’s countermeasure was borrowed from code review culture: every gate decision required a named approver and a one-line evidence note, auditable later. When one provider’s gate-two note turned out to say “client call \u2014 voicemail, did not retry”, the audit caught it, the engagement was paused, and the rule acquired teeth. Controls stay honest the same way tests do: someone has to be able to see them fail.<\/p>\n

    What the case generalises to<\/h2>\n

    Strip the story to its transferable findings and four stand out. First, engagement failures with independent providers cluster in the trust layer, not the skill layer \u2014 so that is where controls belong. Second, every control Verdalia needed already existed in public, battle-tested form; a travel marketplace had simply implemented them as product features rather than process documents. Third, gates must precede money, because direct settlement \u2014 common, legitimate, often preferable \u2014 provides no safety net of its own. Fourth, the pipeline compounds: each verified partner is reusable infrastructure, and the bench grows more valuable with every engagement.<\/p>\n

    The fictional Verdalia got lucky in one respect: its three failures arrived early, cheaply and in the same quarter, forcing the lesson. Real organisations usually absorb the same failures slowly, one per year, each explained away as bad luck. The evidence says otherwise. Luck is not a vendor-management strategy \u2014 and the verification playbook is sitting in plain sight, running millions of stranger-to-stranger bookings, waiting to be copied.<\/p>\n","protected":false},"excerpt":{"rendered":"

    A fictional but familiar case study: three contractor failures in one quarter, and the four-gate verification pipeline that ended them for good.<\/p>\n","protected":false},"author":37,"featured_media":11725,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[147],"tags":[],"class_list":["post-11724","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"yoast_head":"\nCase Study: A Team That Learned to Verify Local Partners - Cotocus<\/title>\n<meta name=\"description\" content=\"A case study in verifying local partners: how one delivery team replaced vibes with a four-gate screening pipeline and measurably cut failures.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Case Study: A Team That Learned to Verify Local Partners - Cotocus\" \/>\n<meta property=\"og:description\" content=\"A case study in verifying local partners: how one delivery team replaced vibes with a four-gate screening pipeline and measurably cut failures.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/\" \/>\n<meta property=\"og:site_name\" content=\"Cotocus\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-03T12:30:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1109482-banner.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Nikhil Farooqui\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Nikhil Farooqui\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/case-study-verifying-local-partners\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/case-study-verifying-local-partners\\\/\"},\"author\":{\"name\":\"Nikhil Farooqui\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\"},\"headline\":\"Case Study: A Team That Learned to Verify Local Partners\",\"datePublished\":\"2026-11-03T12:30:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/case-study-verifying-local-partners\\\/\"},\"wordCount\":1333,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/case-study-verifying-local-partners\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1109482-banner.png\",\"articleSection\":[\"DevOps\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/case-study-verifying-local-partners\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/case-study-verifying-local-partners\\\/\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/case-study-verifying-local-partners\\\/\",\"name\":\"Case Study: A Team That Learned to Verify Local Partners - Cotocus\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/case-study-verifying-local-partners\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/case-study-verifying-local-partners\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1109482-banner.png\",\"datePublished\":\"2026-11-03T12:30:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\"},\"description\":\"A case study in verifying local partners: how one delivery team replaced vibes with a four-gate screening pipeline and measurably cut failures.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/case-study-verifying-local-partners\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/case-study-verifying-local-partners\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/case-study-verifying-local-partners\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1109482-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1109482-banner.png\",\"width\":1200,\"height\":630},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/case-study-verifying-local-partners\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Case Study: A Team That Learned to Verify Local Partners\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/\",\"name\":\"Cotocus\",\"description\":\"Shaping Tomorrow\u2019s Tech Today\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\",\"name\":\"Nikhil Farooqui\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g\",\"caption\":\"Nikhil Farooqui\"},\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/author\\\/nikhil-farooqui\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Case Study: A Team That Learned to Verify Local Partners - Cotocus","description":"A case study in verifying local partners: how one delivery team replaced vibes with a four-gate screening pipeline and measurably cut failures.","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:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/","og_locale":"en_US","og_type":"article","og_title":"Case Study: A Team That Learned to Verify Local Partners - Cotocus","og_description":"A case study in verifying local partners: how one delivery team replaced vibes with a four-gate screening pipeline and measurably cut failures.","og_url":"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/","og_site_name":"Cotocus","article_published_time":"2026-11-03T12:30:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1109482-banner.png","type":"image\/png"}],"author":"Nikhil Farooqui","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Nikhil Farooqui","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/#article","isPartOf":{"@id":"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/"},"author":{"name":"Nikhil Farooqui","@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50"},"headline":"Case Study: A Team That Learned to Verify Local Partners","datePublished":"2026-11-03T12:30:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/"},"wordCount":1333,"commentCount":0,"image":{"@id":"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1109482-banner.png","articleSection":["DevOps"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/","url":"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/","name":"Case Study: A Team That Learned to Verify Local Partners - Cotocus","isPartOf":{"@id":"https:\/\/www.cotocus.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/#primaryimage"},"image":{"@id":"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1109482-banner.png","datePublished":"2026-11-03T12:30:00+00:00","author":{"@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50"},"description":"A case study in verifying local partners: how one delivery team replaced vibes with a four-gate screening pipeline and measurably cut failures.","breadcrumb":{"@id":"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/#primaryimage","url":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1109482-banner.png","contentUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1109482-banner.png","width":1200,"height":630},{"@type":"BreadcrumbList","@id":"https:\/\/www.cotocus.com\/blog\/case-study-verifying-local-partners\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.cotocus.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Case Study: A Team That Learned to Verify Local Partners"}]},{"@type":"WebSite","@id":"https:\/\/www.cotocus.com\/blog\/#website","url":"https:\/\/www.cotocus.com\/blog\/","name":"Cotocus","description":"Shaping Tomorrow\u2019s Tech Today","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.cotocus.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50","name":"Nikhil Farooqui","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g","caption":"Nikhil Farooqui"},"url":"https:\/\/www.cotocus.com\/blog\/author\/nikhil-farooqui\/"}]}},"_links":{"self":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/11724","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/comments?post=11724"}],"version-history":[{"count":1,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/11724\/revisions"}],"predecessor-version":[{"id":11733,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/11724\/revisions\/11733"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/media\/11725"}],"wp:attachment":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/media?parent=11724"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/categories?post=11724"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/tags?post=11724"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}