{"id":340,"date":"2026-06-01T05:00:27","date_gmt":"2026-06-01T05:00:27","guid":{"rendered":"https:\/\/www.plura.ai\/articles\/foreign-robocall-elimination-act-guide"},"modified":"2026-09-02T05:54:49","modified_gmt":"2026-09-02T05:54:49","slug":"foreign-robocall-elimination-act-guide","status":"publish","type":"post","link":"https:\/\/www.plura.ai\/articles\/foreign-robocall-elimination-act-guide","title":{"rendered":"FCC Gateway Provider Obligations and the FREA Proposal"},"content":{"rendered":"<p><em>Written by: Matt Beucler, CEO, Plura AI | Last updated: August 27, 2026<\/em><\/p>\n<h2 id=\"key-takeaways\">Key Takeaways for Gateway and Voice Providers<\/h2>\n<ul>\n<li>U.S. gateway providers must keep RMD registration active, complete annual recertification by March 1, and answer Industry Traceback Group requests within 24 hours under current FCC rules.<sup data-disclaimer-id=\"23\" data-disclaimer-index=\"2\">2<\/sup><\/li>\n<li>SHAKEN\/STIR C-level attestation, four-year KYUP record-keeping, and 10-business-day CORES\/RMD updates remain standing obligations for all voice service providers handling NANP traffic.<\/li>\n<li>Providers may not accept traffic from foreign upstream providers that are not listed in the RMD when calls use U.S. NANP caller ID, and enforcement is active.<\/li>\n<li>The Foreign Robocall Elimination Act (S.2666) has not passed the Senate as of August 2026, so proposed additions such as the $100,000 bond requirement and enhanced traceback immunity are not yet law.<sup data-disclaimer-id=\"26\" data-disclaimer-index=\"4\">4<\/sup><\/li>\n<li>Plura AI delivers carrier-grade voice infrastructure on 100% U.S. soil with built-in SHAKEN\/STIR, DNC scrubbing, and TCPA logging, and you can <a href=\"https:\/\/www.plura.ai\/plura-webchat\" target=\"_blank\">talk with our team<\/a> to strengthen your compliance posture.<sup data-disclaimer-id=\"22\" data-disclaimer-index=\"1\">1<\/sup><\/li>\n<\/ul>\n<h2>Current FCC Gateway Provider Obligations in Effect Today<\/h2>\n<p>The following ten items reflect enacted rules under the TRACED Act and subsequent FCC orders.<sup data-disclaimer-id=\"23\" data-disclaimer-index=\"2\">2<\/sup> Each item is in force as of August 27, 2026, and together they form the baseline compliance framework that every U.S. gateway provider must maintain to reduce enforcement risk.<\/p>\n<ol>\n<li><strong>RMD Registration.<\/strong> All voice service providers (VSPs) interconnected with the public switched telephone network (PSTN) and furnishing voice communications using North American Numbering Plan (NANP) resources must register in the FCC Robocall Mitigation Database (RMD). The RMD is the public registry where providers certify their SHAKEN\/STIR implementation status or upload a written mitigation program. Gateway providers handling foreign-originated traffic had a compliance deadline of January 11, 2023 for RMD registration.<\/li>\n<li><strong>Annual RMD Recertification by March 1.<\/strong> The FCC requires all providers with current RMD filings to complete <a href=\"https:\/\/vantagepnt.com\/news\/alert-robocall-mitigation-database-annual-recertification-due-march-2-2026\/\" target=\"_blank\" rel=\"noindex nofollow\">mandatory annual recertification by March 1 each year, or the next business day if March 1 falls on a weekend<\/a>. Recertification verifies the accuracy of company information, mitigation programs, SHAKEN\/STIR certifications, and contact details. The recertification window opens February 1.<\/li>\n<li><strong>SHAKEN\/STIR Gateway (C-Level) Attestation.<\/strong> SHAKEN\/STIR (Secure Telephone Identity Revisited \/ Signature-based Handling of Asserted information using toKENs) is the caller ID authentication framework mandated under the TRACED Act. Gateway providers handling foreign-originated traffic that cannot verify the call&#8217;s origin assign a <a href=\"https:\/\/leadcompliant.com\/articles\/tools-and-processes\/fcc-robocall-mitigation-database-registration-how-to-complete-it\" target=\"_blank\" rel=\"noindex nofollow\">C-level (Gateway) attestation<\/a>, which indicates the call entered the network at a known point. The FCC has also proposed requiring terminating providers to transmit verified caller identity information whenever an A-level attestation is indicated. That rulemaking remains pending.<\/li>\n<li><strong>24-Hour Industry Traceback Group Response.<\/strong> Providers must respond to traceback requests from the Industry Traceback Group (ITG) within 24 hours. The ITG is the FCC-designated consortium that investigates illegal robocall traffic. Timely action can influence enforcement outcomes, as shown when the FCC applied a downward adjustment to the proposed forfeiture against Voxbeam Telecommunications because the provider blocked traffic within 24 hours of the first ITG traceback request.<\/li>\n<li><strong>KYUP Record-Keeping for Four Years.<\/strong> The Know-Your-Upstream-Provider (KYUP) rule requires voice service providers to take reasonable and effective steps to ensure upstream providers are not using the provider to carry a high volume of illegal traffic. Providers must retain records that support KYUP compliance for four years. The FCC&#8217;s May 2026 Further Notice of Proposed Rulemaking (FNPRM) in WC Docket No. 17-97 proposes expanding these obligations further, but those proposals are not yet final rules.<\/li>\n<li><strong>10-Business-Day CORES\/RMD Update Requirement.<\/strong> All FCC Registration Number (FRN) holders must <a href=\"https:\/\/jsitel.com\/resource\/fcc-requires-annual-robocall-mitigation-database-recertification-by-march-1-2026\" target=\"_blank\" rel=\"noindex nofollow\">update their CORES (Commission Registration System) and RMD information within 10 business days of any change<\/a> to company details, contact information, or mitigation program status.<\/li>\n<li><strong>$10,000 Base Forfeiture for False RMD Information.<\/strong> The FCC has set a <a href=\"https:\/\/viirtue.com\/robocall-mitigation-and-kyc-for-voip-resellers-a-2026-compliance-guide\" target=\"_blank\" rel=\"noindex nofollow\">$10,000 base forfeiture for each submission of false or inaccurate information<\/a> to the RMD. Providers that certify an incorrect operational role, as Voxbeam did by certifying it was not a gateway provider, face compounded enforcement exposure.<\/li>\n<li><strong>$1,000 Per-Day Forfeiture for Late Updates.<\/strong> Under <a href=\"https:\/\/viirtue.com\/robocall-mitigation-and-kyc-for-voip-resellers-a-2026-compliance-guide\" target=\"_blank\" rel=\"noindex nofollow\">FCC 24-135 (effective February 5, 2026)<\/a>, failure to update RMD or CORES information within 10 business days triggers a $1,000 forfeiture per violation. Non-compliance can also result in removal from the RMD and mandatory traffic blocking by downstream carriers.<\/li>\n<li><strong>Downstream Blocking of Unregistered Foreign Traffic.<\/strong> Intermediate and terminating providers must block all voice traffic from any originating or gateway provider not listed in the RMD within 30 days of the provider appearing on the FCC&#8217;s non-compliant list. Enforcement of the prohibition on accepting traffic from foreign providers not in the RMD when calls use U.S. NANP resources is in effect.<\/li>\n<li><strong>Verification of Upstream Foreign Providers in RMD Before Accepting NANP Calls.<\/strong> Under 47 C.F.R. \u00a7 64.6305(g)(2), U.S. providers are barred from accepting traffic directly from a foreign provider not listed in the RMD when the calls use U.S. NANP resources in the caller ID field. Gateway providers must implement systems that automatically require RMD verification of any foreign upstream provider before traffic is accepted. The mitigation plan filed in the RMD must also describe customer vetting practices, traffic monitoring for suspicious patterns, and the provider&#8217;s traceback response process.<\/li>\n<\/ol>\n<p><a href=\"https:\/\/plura.ai\/pricing\" target=\"_blank\"><strong>Compare plans operating on 100% U.S. infrastructure at Plura AI&#8217;s pricing page.<\/strong><\/a><\/p>\n<h2>Proposed FREA Additions and Readiness Planning<\/h2>\n<p><strong>Bill status as of August 2026:<\/strong> The Foreign Robocall Elimination Act (S.2666) has not passed the Senate. No House action has occurred, and the bill has not been enacted into law. The items below describe proposed requirements only. Readers should consult qualified legal counsel regarding their organization&#8217;s obligations under current law.<\/p>\n<p>The following proposed additions are drawn from S.2666 and incorporate <a href=\"https:\/\/markey.senate.gov\/news\/press-releases\/senate-passes-markey-amendments-to-crack-down-on-illegal-robocalls\" target=\"_blank\" rel=\"noindex nofollow\">four amendments secured during committee consideration<\/a>.<\/p>\n<ul>\n<li><strong>$100,000 Bond Requirement (Proposed).<\/strong> S.2666 would direct the FCC to require certain voice service providers to post a bond of up to $100,000 before certifying to the RMD that they are implementing robocall mitigation measures. Any increase in revenues from forfeited bonds is projected to be insignificant. This requirement is not current law. Readiness action: review bonding capacity and surety relationships in anticipation of a potential FCC rulemaking if the bill is enacted.<\/li>\n<li><strong>FCC-DOJ-FTC Robocall Task Force (Proposed).<\/strong> The bill would direct the FCC, in coordination with the FTC and DOJ, to establish a task force on unlawful robocalls that reports to Congress within 360 days of establishment on the most effective ways to combat them. Readiness action: monitor task force establishment and any resulting recommendations that may inform future rulemaking.<\/li>\n<li><strong>Traceback Consortium Immunity (Proposed).<\/strong> A Thune-Markey amendment incorporated into S.2666 would <a href=\"https:\/\/markey.senate.gov\/news\/press-releases\/senate-passes-markey-amendments-to-crack-down-on-illegal-robocalls\" target=\"_blank\" rel=\"noindex nofollow\">grant the registered industry traceback consortium immunity from prosecution<\/a> for publishing information on suspected fraudulent, abusive, or unlawful robocalls. The CBO notes this limits private entities&#8217; rights of action for damages related to such sharing. Readiness action: no direct operational change is required, but traceback investigations may become more active if immunity is enacted.<\/li>\n<li><strong>Enhanced Transparency Reporting on Traceback Results (Proposed).<\/strong> Two Markey-Lujan amendments in S.2666 would <a href=\"https:\/\/markey.senate.gov\/news\/press-releases\/senate-passes-markey-amendments-to-crack-down-on-illegal-robocalls\" target=\"_blank\" rel=\"noindex nofollow\">direct the robocall task force to evaluate the benefits and risks of periodically releasing traceback results<\/a> to improve transparency and deterrence. Readiness action: assess internal documentation practices for traceback response records, because periodic public disclosure of traceback results could affect provider reputation.<\/li>\n<\/ul>\n<p>Separately, the FCC&#8217;s May 2026 FNPRM in WC Docket No. 17-97 proposes expanded KYUP information-collection requirements, including verification of whether an upstream provider is owned by or subject to the jurisdiction of a foreign adversary. That rulemaking is also pending and not yet final.<\/p>\n<h2>Infrastructure Strategy for Gateway Providers<\/h2>\n<p>Plura AI is an FCC-licensed audio bridging carrier. Voice originates on Plura&#8217;s own domestic infrastructure, not through a third-party Communications Platform as a Service (CPaaS). That distinction has direct operational relevance for gateway providers that are evaluating their infrastructure posture under current FCC rules and proposed additions.<\/p>\n<figure style=\"text-align: center\"><img decoding=\"async\" src=\"https:\/\/cdn.aigrowthmarketer.co\/1779337911454-8c3a9645d906.png\" alt=\"Screenshot of Plura\u2019s fully compliant AI communications platform showing business registration and phone number provisioning workflows for AI Voice, SMS, RCS, and Webchat communication automation.\" style=\"max-height: 500px\" loading=\"lazy\"><figcaption><em>Plura\u2019s FCC-licensed AI communications platform simplifies compliant business registration and phone number provisioning for AI Voice, SMS, RCS, and Webchat workflows.<\/em><\/figcaption><\/figure>\n<p>Plura&#8217;s platform runs on 100% U.S. infrastructure by architecture, which means voice origination, model hosting, data storage, and call recording all sit on domestic infrastructure without foreign routing points. This domestic-only architecture enables SHAKEN\/STIR authentication to run at the carrier level on every outbound call, with branded caller ID issued directly through Plura&#8217;s FCC-licensed carrier identity rather than through a reseller. Because compliance features are built into the carrier layer rather than bolted on afterward, real-time DNC (Do Not Call) scrubbing, TCPA (Telephone Consumer Protection Act, 47 U.S.C. \u00a7 227) consent logging, and automated quiet-hours enforcement operate as first-class platform capabilities, not third-party add-ons.<\/p>\n<p>For operators evaluating the FCC&#8217;s proposed foreign adversary provisions in the KYUP FNPRM, Plura&#8217;s domestic infrastructure architecture means voice traffic does not route through foreign-controlled infrastructure. Plura supports customer compliance efforts, and customers remain responsible for their own regulatory obligations and certifications.<\/p>\n<figure style=\"text-align: center\"><img decoding=\"async\" src=\"https:\/\/cdn.aigrowthmarketer.co\/1779339090994-980045ddacd2.png\" alt=\"Plura Security &amp; Compliance dashboard highlighting SOC 2, ISO, and GDPR standards with secure trust verification management.\" style=\"max-height: 500px\" loading=\"lazy\"><figcaption><em>Plura Security &amp; Compliance supports SOC 2, ISO, and GDPR standards with trust registration, verification management, and secure AI communications.<\/em><\/figcaption><\/figure>\n<p>Plura&#8217;s <a href=\"https:\/\/plura.ai\/ai-predictive-dialer\" target=\"_blank\" rel=\"noindex nofollow\">AI Predictive Dialer<\/a> and <a href=\"https:\/\/plura.ai\/ai-voice-demo\" target=\"_blank\" rel=\"noindex nofollow\">AI voice agent<\/a> capabilities operate on this same carrier-grade foundation, with SOC 2, HIPAA, and ISO certification covering the underlying infrastructure.<sup data-disclaimer-id=\"22\" data-disclaimer-index=\"1\">1<\/sup><\/p>\n<figure style=\"text-align: center\"><img decoding=\"async\" src=\"https:\/\/cdn.aigrowthmarketer.co\/1779338793506-2d33c5dff8e8.png\" alt=\"Plura Predictive Dialer dashboard displaying AI-powered outbound call pacing, transfer analysis, and dialing performance insights.\" style=\"max-height: 500px\" loading=\"lazy\"><figcaption><em>Plura Predictive Dialer automates outbound calling with AI-powered pacing, transfer optimization, and real-time performance analytics.<\/em><\/figcaption><\/figure>\n<p><a href=\"https:\/\/plura.ai\/pricing\" target=\"_blank\"><strong>Review Plura&#8217;s carrier-grade pricing and compliance features.<\/strong><\/a><\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Foreign Robocall Elimination Act Legislative Status<\/h3>\n<p>No. As of August 27, 2026, S.2666 has not been enacted. S.2666 has not passed the Senate and awaits further consideration by the House of Representatives. No House vote has occurred, and the bill has not been presented to the President for signature. Gateway providers should continue operating under current FCC rules and consult qualified legal counsel regarding any compliance planning tied to the bill&#8217;s proposed provisions.<\/p>\n<h3>Consequences of Accepting Traffic from Unregistered Foreign Providers<\/h3>\n<p>Under 47 C.F.R. \u00a7 64.6305(g)(2), U.S. providers are prohibited from accepting traffic directly from a foreign provider not listed in the RMD when the calls use U.S. NANP resources in the caller ID field. Enforcement of this rule is in effect. In April 2026, the FCC proposed a $4.5 million forfeiture against Voxbeam Telecommunications for transmitting tens of thousands of calls from Axfone, a foreign provider never listed in the RMD.<sup data-disclaimer-id=\"25\" data-disclaimer-index=\"3\">3<\/sup> The FCC proposed the forfeiture amount based on calls that used U.S. NANP caller ID and reached U.S. subscribers. Providers that block traffic promptly after a traceback request may receive downward adjustments, as Voxbeam did for blocking within 24 hours. Organizations should consult qualified legal counsel regarding their specific obligations.<\/p>\n<h3>Impact of the Proposed $100,000 Bond Requirement<\/h3>\n<p>If enacted, S.2666 would direct the FCC to require certain voice service providers to post a bond of up to $100,000 before certifying to the RMD that they are implementing robocall mitigation measures. The FCC would determine the specific bond amount. The Congressional Budget Office cost estimate projects that revenues from forfeited bonds would be insignificant, and that implementation costs for the FCC, FTC, and DOJ would be negligible. Because S.2666 has not been enacted, this requirement is not in effect. If the bill becomes law, the FCC would need to issue implementing rules before the bond requirement would apply. Providers should monitor House action and any subsequent FCC rulemaking and consult qualified legal counsel for guidance on their specific situation.<\/p>\n<h3>Current KYUP Rule Compared with Proposed FNPRM Expansion<\/h3>\n<p>The current KYUP rule requires voice service providers to take reasonable and effective steps to ensure upstream originating or intermediate providers are not using the provider to carry a high volume of illegal traffic. The FCC&#8217;s May 2026 FNPRM in WC Docket No. 17-97 proposes to establish baseline KYUP information-collection, compliance review, verification, monitoring, and responsive-action requirements. The proposed rules would require providers to collect general business information, financial information, ownership and affiliate details including ultimate beneficial owners with 10 percent or more stake, operational records, and service information from upstream providers before entering new agreements, renewing existing agreements, or upon receiving adverse information.<\/p>\n<p>The FNPRM also proposes that providers determine whether an upstream provider is owned by, controlled by, or subject to the jurisdiction of a foreign adversary. These proposed requirements are not yet final rules. The FCC proposes that new KYUP rules take effect the later of 12 months after Federal Register publication of a Report and Order or 30 days after OMB approval of any new information collections. Organizations should consult qualified legal counsel regarding current obligations and readiness planning for proposed additions.<\/p>\n<h2>Conclusion: Acting on Current Rules While Tracking What Comes Next<\/h2>\n<p>The distinction between current FCC obligations and proposed legislation is operationally significant for U.S. voice and gateway providers. The ten-item checklist above reflects enacted rules under the TRACED Act and subsequent FCC orders, including RMD registration and annual recertification, SHAKEN\/STIR C-level attestation, 24-hour ITG traceback response, KYUP record-keeping, 10-business-day CORES\/RMD update requirements, and the prohibition on accepting traffic from foreign providers not listed in the RMD. These obligations are in force now.<\/p>\n<p>The proposed FREA additions described earlier remain pending legislation. The $100,000 bond concept, the FCC-DOJ-FTC robocall task force, traceback consortium immunity, and enhanced transparency reporting are not current law. Providers should monitor House action and any subsequent FCC rulemaking if the bill is enacted.<\/p>\n<p>The FCC&#8217;s regulatory activity in 2026 also includes the May 2026 KYUP FNPRM, the July 2026 RMD FNPRM proposing expanded filing obligations and a one-step removal process, and the March 2026 Call Center Onshoring NPRM. Each of these rulemakings is pending and not yet final. The FCC has also proposed, in a separate rulemaking, that voice service providers implement measures so that consumers know which calls originate from outside the United States and that providers avoid spoofing of U.S. telephone numbers for calls that originate from outside the United States.<\/p>\n<p>Plura operates on 100% U.S. infrastructure by architecture, with SHAKEN\/STIR authentication, branded caller ID issuance, real-time DNC scrubbing, and TCPA consent logging built into the platform at the carrier level. As noted in the infrastructure discussion, customers retain responsibility for their own compliance posture.<\/p>\n<p><a href=\"https:\/\/plura.ai\/pricing\" target=\"_blank\"><strong>Explore Plura&#8217;s domestic infrastructure plans and pricing.<\/strong><\/a><\/p>\n<hr data-disclaimer-divider=\"true\">\n<div data-disclaimer-footer=\"true\">\n<p data-disclaimer-id=\"22\" data-disclaimer-type=\"content_based\"><sup data-disclaimer-index=\"1\">1<\/sup> Plura AI maintains SOC 2, HIPAA, ISO, and GDPR posture as part of its platform infrastructure. References to compliance frameworks in this article describe Plura\u2019s platform capabilities and do not constitute a guarantee that any customer using Plura will themselves be compliant with applicable laws or standards. Customers remain solely responsible for their own regulatory obligations, certifications, consent management, recordkeeping, and the claims they make to their own end users. Consult qualified legal counsel for guidance specific to your use case.<\/p>\n<p data-disclaimer-id=\"23\" data-disclaimer-type=\"content_based\"><sup data-disclaimer-index=\"2\">2<\/sup> This article describes regulatory frameworks at a general level and does not constitute legal advice. Laws and regulations vary by jurisdiction, change over time, and apply differently depending on facts and circumstances. Readers should consult qualified legal counsel before making compliance decisions.<\/p>\n<p data-disclaimer-id=\"25\" data-disclaimer-type=\"content_based\"><sup data-disclaimer-index=\"3\">3<\/sup> References to third-party products, services, companies, or research are made for informational and comparative purposes only. Plura AI is not affiliated with, endorsed by, or sponsored by any third party named in this article unless explicitly stated. Trademarks and product names referenced remain the property of their respective owners.<\/p>\n<p data-disclaimer-id=\"26\" data-disclaimer-type=\"content_based\"><sup data-disclaimer-index=\"4\">4<\/sup> This article contains forward-looking statements regarding industry trends, technology adoption, and future capabilities. These statements reflect current expectations and are subject to change. Plura AI undertakes no obligation to update forward-looking statements except as required.<\/p>\n<p data-disclaimer-id=\"21\" data-disclaimer-type=\"fixed\">This article is provided for informational purposes only and reflects Plura AI\u2019s understanding at the time of publication. Product capabilities, integrations, and specifications are subject to change. For the most current information, visit plura.ai.<\/p>\n<p data-disclaimer-id=\"27\" data-disclaimer-type=\"fixed\">This article was produced with the assistance of AI tools and reviewed by Plura AI prior to publication.<\/p>\n<\/div>\n<section data-read-next=\"true\">\n<h2>Read Next<\/h2>\n<ul>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/foreign-robocall-act-carrier-requirements\" target=\"_blank\">S.2666 FREA and 47 CFR 64.6305: Gateway Provider Guide<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/foreign-robocall-elimination-fcc-guidelines\" target=\"_blank\">Foreign Robocall Elimination Act FCC Guidelines for Gateways<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/foreign-robocall-elimination-act-compliance\" target=\"_blank\">Foreign Robocall Elimination Act: Practical Compliance Guide<\/a><\/li>\n<li><a href=\"https:\/\/www.plura.ai\/articles\/foreign-robocall-elimination-act-provisions\" target=\"_blank\">Foreign Robocall Elimination Act: 4 Key Provisions<\/a><\/li>\n<\/ul>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>Review current FCC gateway provider rules and proposed FREA changes. Plura AI supports voice providers in building compliant-ready infrastructure.<\/p>\n","protected":false},"author":106,"featured_media":339,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[2],"tags":[],"class_list":["post-340","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-contact-centers"],"_links":{"self":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/340","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/comments?post=340"}],"version-history":[{"count":2,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/340\/revisions"}],"predecessor-version":[{"id":2452,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/posts\/340\/revisions\/2452"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media\/339"}],"wp:attachment":[{"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/media?parent=340"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/categories?post=340"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.plura.ai\/articles\/wp-json\/wp\/v2\/tags?post=340"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}