{"id":1141,"date":"2026-11-07T07:01:04","date_gmt":"2026-11-07T12:01:04","guid":{"rendered":"https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/"},"modified":"2026-11-07T07:01:04","modified_gmt":"2026-11-07T12:01:04","slug":"should-msps-charge-for-after-hours-support","status":"publish","type":"post","link":"https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/","title":{"rendered":"Should MSPs Charge for After-Hours Support? Price the Pager, Not Just the Hours"},"content":{"rendered":"<p>It&#039;s 11:40 on a Tuesday night and a client&#039;s office manager calls the support line because the shared printer won&#039;t print payroll stubs. Your on-call tech fixes it in twelve minutes from the couch. Next month the client&#039;s invoice looks exactly like last month&#039;s. Was that call included? Billable? Nobody can say, because the agreement says &quot;after-hours support available&quot; and nothing else, and the tech meant to write a ticket in the morning.<\/p>\n<p>Yes, MSPs should charge for after-hours support. But the multiplier is the easy part. The decision that actually protects your margin is charging for two different things: the <strong>availability<\/strong> (someone carrying the phone all week, whether it rings or not) and the <strong>work<\/strong> (the calls that come in). Most MSPs price only the work, and most agreements don&#039;t say which calls count.<\/p>\n<h2>The short answer<\/h2>\n<ul>\n<li><strong>Put a defined set of emergencies inside the agreement<\/strong>, and price the on-call cost into the monthly fee.<\/li>\n<li><strong>Bill everything else after hours at a multiplier with a minimum<\/strong>, stated in the agreement before the first call.<\/li>\n<li><strong>Make every after-hours call end in a ticket<\/strong>, or you can&#039;t bill it, count it, or tell whether the client is worth the coverage.<\/li>\n<\/ul>\n<h2>What the common advice gets right, and what it skips<\/h2>\n<p>The vendor guides that rank for this question agree on the rate. <a href=\"https:\/\/www.itglue.com\/blog\/msps-after-hours-support\/\">IT Glue&#039;s guide<\/a> says requests outside business hours &quot;may not be included in the basic service contract and can be billed on an hourly basis,&quot; and that you &quot;may charge 1.5 or 2 times the regular price.&quot; <a href=\"https:\/\/onpage.com\/onpage-guide-how-to-handle-after-hours-support-for-msps\/amp\">OnPage&#039;s guide<\/a> gives the same 8-to-5 baseline and 1.5x after 5 p.m. and on weekends.<\/p>\n<p>That&#039;s a reasonable starting point. What none of them gives you is a minimum, a definition of an emergency, or the cost of keeping someone on call in the first place. Those three decide whether after-hours support makes money.<\/p>\n<h2>Price the pager, not just the hours<\/h2>\n<p>The cost of after-hours coverage starts before anyone calls. Somebody has to carry the phone, stay sober enough to log in, and answer within whatever window you promised.<\/p>\n<p>Most MSPs that take on-call seriously pay for that. In an <a href=\"https:\/\/www.reddit.com\/r\/msp\/comments\/1i5t3r2\/do_you_pay_staff_to_be_oncall_after_hours\/\">r\/msp thread on on-call pay<\/a>, owners and techs described weekly stipends from $50 to $225, usually plus overtime for time actually worked; one said their $125 weekly rate hadn&#039;t changed in &quot;over 15 years,&quot; and another paid &quot;$50 per call answered&quot; with an answering service taking first contact. Those are anecdotes from shops of unknown size, not a benchmark, but the pattern is clear: availability costs money every week of the year, quiet or not.<\/p>\n<p>So run the arithmetic on your own number. As an example, a $150 weekly stipend is $7,800 a year before a single call is worked. Spread across 20 managed clients, that&#039;s about $33 per client per month just to have the phone answered. If your agreement says after-hours emergencies are included and your price doesn&#039;t carry that cost, you&#039;re paying it out of margin.<\/p>\n<p>That&#039;s the case for a line in the agreement (or a higher tier) that covers availability, separate from the hourly multiplier for work. It also answers the client who asks why they pay for after-hours coverage they rarely use: they&#039;re paying for the phone being answered, the same way they pay for insurance.<\/p>\n<h2>Define the emergency before 2 a.m., not during<\/h2>\n<p>&quot;Emergency support included&quot; without a definition means every call is an emergency. The caller decides, at the worst possible time, and your tech isn&#039;t going to argue with a client at midnight.<\/p>\n<p>Write the definition in terms the client can check before they call:<\/p>\n<ul>\n<li><strong>Included emergencies:<\/strong> the whole office can&#039;t work (internet, email or the line-of-business app down for everyone), a server or firewall is down, or a suspected security incident.<\/li>\n<li><strong>Billable after hours:<\/strong> anything affecting one user or one device, scheduled work the client asked to move to evening, and &quot;while you&#039;re on, can you also\u2026&quot; requests.<\/li>\n<li><strong>Next business day:<\/strong> everything else, unless the client agrees to the billable rate on the call.<\/li>\n<\/ul>\n<p>Then set the rate and the minimum per work type, not one number for everything. We covered this in <a href=\"https:\/\/vight.ai\/blog\/msp-billing-increments\/\">should MSPs bill in 15-minute increments<\/a>: remote daytime work can carry a small minimum, but an after-hours callout should carry one that reflects pulling someone off their evening. In the r\/msp thread, one owner paid techs 1.5x overtime &quot;with a 1 hour minimum for ALL calls.&quot; Whatever you pick, a minimum is what stops the twelve-minute printer fix from costing more in disruption than it brings in.<\/p>\n<p>The printer call from the opening fails the emergency test (one device, one user, nothing down for the office). Under this definition it&#039;s billable at the after-hours rate, or it waits until morning. Either answer is fine. &quot;Nobody knows&quot; isn&#039;t.<\/p>\n<h2>The call that never becomes a ticket<\/h2>\n<p>Here&#039;s the failure point the pricing guides miss entirely. You can have a perfect after-hours clause and still not bill a dime of it, because after-hours work is the work least likely to reach the PSA.<\/p>\n<p>The on-call tech handles the call from their phone, maybe from a personal cell, fixes it, and plans to write it up in the morning. In the morning there are new tickets. The call never becomes a ticket or a time entry, so it doesn&#039;t show up on the invoice, the client&#039;s effective hourly rate looks better than it is, and at renewal you can&#039;t show the client the six midnight calls they made last quarter. We walked through how this inflates per-client margins in <a href=\"https:\/\/vight.ai\/blog\/msp-profit-margins\/\">MSP profit margins<\/a>, and why the phone is where time goes missing in <a href=\"https:\/\/vight.ai\/blog\/msp-time-tracking\/\">MSP time tracking<\/a>.<\/p>\n<p>Three rules fix most of it:<\/p>\n<ol>\n<li><strong>After-hours calls go to one number<\/strong> that routes to whoever is on call, not to techs&#039; personal cells. Then the phone system has a log you can check.<\/li>\n<li><strong>No after-hours fix without a ticket<\/strong>, opened during the call or before the tech goes back to bed, with the work type set to after-hours so the PSA bills it at the right rate.<\/li>\n<li><strong>Review after-hours calls against tickets weekly.<\/strong> Pull the call log for the on-call line and look for calls with no matching ticket. It&#039;s tedious by hand, which is why a <a href=\"https:\/\/vight.ai\/phone-to-psa\">phone-to-PSA gap check<\/a> is worth running before you rewrite any pricing.<\/li>\n<\/ol>\n<p>If your SOPs don&#039;t already cover the on-call handoff, add it; it&#039;s one of the ones in <a href=\"https:\/\/vight.ai\/blog\/msp-sop\/\">MSP SOPs: write the ones that end in a ticket first<\/a>.<\/p>\n<h2>Should after-hours support be included at all?<\/h2>\n<p>It depends on the client, which is why it belongs in your tiers rather than in every agreement. A dental office that closes at 5 and never works weekends doesn&#039;t need to pay for availability; give them next-business-day support and a published callout rate. A manufacturer running a second shift, or a client with staff in other time zones, needs coverage they can count on, and should pay for it in the monthly fee. <a href=\"https:\/\/vight.ai\/blog\/msp-pricing-models\/\">MSP pricing models<\/a> covers how to put after-hours in writing as an exception or a tier, whichever pricing unit you use.<\/p>\n<p>The one thing to avoid is the middle: &quot;after-hours available&quot; on the proposal, no price, no definition. That&#039;s free 24\/7 support for whichever client calls the most.<\/p>\n<h2>Where tooling helps<\/h2>\n<p>None of this needs new software to start. A routed on-call number, a work type for after-hours in your PSA, and a weekly check will get most MSPs most of the way.<\/p>\n<p>If the gap is that nobody wants to answer the phone at 2 a.m. for a call that turns out to be a printer, that&#039;s where an answering layer helps. Vight&#039;s AI voice agent can answer after-hours calls on a Vight phone number, ask follow-up questions, capture the caller&#039;s details and open a ticket with the context in ConnectWise, Autotask, HaloPSA or Syncro. Its after-hours escalation agent summarizes those calls, decides whether they need someone now, and pages whoever is on call on your on-call schedule (role by role, by email, Teams, Slack, SMS or phone call) until someone acknowledges the ticket. That doesn&#039;t decide your policy, but it means the urgent call reaches a person and the printer call becomes a ticket for the morning, with a record either way.<\/p>\n<p>If you want to see how that would fit your current on-call setup, <a href=\"https:\/\/vight.ai\/demo\">book a demo<\/a>.<\/p>\n<h2>FAQ<\/h2>\n<p><strong>How much should an MSP charge for after-hours support?<\/strong><br \/>Vendor guides commonly suggest 1.5x to 2x your standard hourly rate for after-hours work, with a minimum per callout. Price the on-call availability separately, from what you actually pay techs to be on call each week, divided across the clients who get the coverage.<\/p>\n<p><strong>Should after-hours support be included in a managed services agreement?<\/strong><br \/>Include a defined list of emergencies (office-wide outages, server or firewall down, suspected security incidents) and price the on-call cost into the fee. Bill other after-hours requests at a stated rate, or move them to the next business day.<\/p>\n<p><strong>What counts as an after-hours emergency for an MSP?<\/strong><br \/>Write it in terms the client can check before calling: something that stops the whole office or a critical system, or a possible security incident. Problems affecting one user or one device usually aren&#039;t emergencies.<\/p>\n<p><strong>Why don&#039;t MSPs bill for after-hours work they do?<\/strong><br \/>Usually because the work never becomes a ticket or a time entry. On-call techs handle calls from their phones and mean to document them later. Route after-hours calls to one number and require a ticket for every call so the PSA can bill it.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It&#039;s 11:40 on a Tuesday night and a client&#039;s office manager calls the support line because the shared printer won&#039;t print payroll stubs. Your on-call tech fixes it in twelve minutes from the couch. Next month the client&#039;s invoice looks exactly like last month&#039;s. Was that call included? Billable? Nobody can say, because the agreement [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1141","post","type-post","status-publish","format-standard","hentry","category-msp-operations"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Should MSPs Charge for After-Hours Support? Price the Pager, Not Just the Hours<\/title>\n<meta name=\"description\" content=\"Yes, but charge for on-call availability and the work separately, define the emergency, and make every after-hours call end in a ticket.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Should MSPs Charge for After-Hours Support? Price the Pager, Not Just the Hours\" \/>\n<meta property=\"og:description\" content=\"Yes, but charge for on-call availability and the work separately, define the emergency, and make every after-hours call end in a ticket.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/\" \/>\n<meta property=\"og:site_name\" content=\"Vight Insights | AI for MSPs\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-07T12:01:04+00:00\" \/>\n<meta name=\"author\" content=\"Nathan Spitalny\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Nathan Spitalny\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/should-msps-charge-for-after-hours-support\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/should-msps-charge-for-after-hours-support\\\/\"},\"author\":{\"name\":\"Nathan Spitalny\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#\\\/schema\\\/person\\\/d256cba1d191205aed6403d4604a2794\"},\"headline\":\"Should MSPs Charge for After-Hours Support? Price the Pager, Not Just the Hours\",\"datePublished\":\"2026-11-07T12:01:04+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/should-msps-charge-for-after-hours-support\\\/\"},\"wordCount\":1646,\"publisher\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#organization\"},\"articleSection\":[\"MSP Operations\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/should-msps-charge-for-after-hours-support\\\/\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/should-msps-charge-for-after-hours-support\\\/\",\"name\":\"Should MSPs Charge for After-Hours Support? Price the Pager, Not Just the Hours\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#website\"},\"datePublished\":\"2026-11-07T12:01:04+00:00\",\"description\":\"Yes, but charge for on-call availability and the work separately, define the emergency, and make every after-hours call end in a ticket.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/should-msps-charge-for-after-hours-support\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/vight.ai\\\/blog\\\/should-msps-charge-for-after-hours-support\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/should-msps-charge-for-after-hours-support\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/vight.ai\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Should MSPs Charge for After-Hours Support? Price the Pager, Not Just the Hours\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/\",\"name\":\"Vight Insights | AI for MSPs\",\"description\":\"AI Automation, MSP Growth Strategies &amp; Smarter IT Operations\",\"publisher\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/vight.ai\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#organization\",\"name\":\"Vight Insights | AI for MSPs\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/vight-logo-square.png\",\"contentUrl\":\"https:\\\/\\\/vight.ai\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/vight-logo-square.png\",\"width\":800,\"height\":800,\"caption\":\"Vight Insights | AI for MSPs\"},\"image\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#\\\/schema\\\/person\\\/d256cba1d191205aed6403d4604a2794\",\"name\":\"Nathan Spitalny\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g\",\"caption\":\"Nathan Spitalny\"},\"sameAs\":[\"http:\\\/\\\/127.0.0.1\"],\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/author\\\/user\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Should MSPs Charge for After-Hours Support? Price the Pager, Not Just the Hours","description":"Yes, but charge for on-call availability and the work separately, define the emergency, and make every after-hours call end in a ticket.","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:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/","og_locale":"en_US","og_type":"article","og_title":"Should MSPs Charge for After-Hours Support? Price the Pager, Not Just the Hours","og_description":"Yes, but charge for on-call availability and the work separately, define the emergency, and make every after-hours call end in a ticket.","og_url":"https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/","og_site_name":"Vight Insights | AI for MSPs","article_published_time":"2026-11-07T12:01:04+00:00","author":"Nathan Spitalny","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Nathan Spitalny","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/#article","isPartOf":{"@id":"https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/"},"author":{"name":"Nathan Spitalny","@id":"https:\/\/vight.ai\/blog\/#\/schema\/person\/d256cba1d191205aed6403d4604a2794"},"headline":"Should MSPs Charge for After-Hours Support? Price the Pager, Not Just the Hours","datePublished":"2026-11-07T12:01:04+00:00","mainEntityOfPage":{"@id":"https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/"},"wordCount":1646,"publisher":{"@id":"https:\/\/vight.ai\/blog\/#organization"},"articleSection":["MSP Operations"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/","url":"https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/","name":"Should MSPs Charge for After-Hours Support? Price the Pager, Not Just the Hours","isPartOf":{"@id":"https:\/\/vight.ai\/blog\/#website"},"datePublished":"2026-11-07T12:01:04+00:00","description":"Yes, but charge for on-call availability and the work separately, define the emergency, and make every after-hours call end in a ticket.","breadcrumb":{"@id":"https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/vight.ai\/blog\/should-msps-charge-for-after-hours-support\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/vight.ai\/blog\/"},{"@type":"ListItem","position":2,"name":"Should MSPs Charge for After-Hours Support? Price the Pager, Not Just the Hours"}]},{"@type":"WebSite","@id":"https:\/\/vight.ai\/blog\/#website","url":"https:\/\/vight.ai\/blog\/","name":"Vight Insights | AI for MSPs","description":"AI Automation, MSP Growth Strategies &amp; Smarter IT Operations","publisher":{"@id":"https:\/\/vight.ai\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/vight.ai\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/vight.ai\/blog\/#organization","name":"Vight Insights | AI for MSPs","url":"https:\/\/vight.ai\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/vight.ai\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/vight-logo-square.png","contentUrl":"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/vight-logo-square.png","width":800,"height":800,"caption":"Vight Insights | AI for MSPs"},"image":{"@id":"https:\/\/vight.ai\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/vight.ai\/blog\/#\/schema\/person\/d256cba1d191205aed6403d4604a2794","name":"Nathan Spitalny","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g","caption":"Nathan Spitalny"},"sameAs":["http:\/\/127.0.0.1"],"url":"https:\/\/vight.ai\/blog\/author\/user\/"}]}},"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/posts\/1141","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/comments?post=1141"}],"version-history":[{"count":0,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/posts\/1141\/revisions"}],"wp:attachment":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/media?parent=1141"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/categories?post=1141"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/tags?post=1141"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}