{"id":17667,"date":"2026-03-20T05:06:07","date_gmt":"2026-03-20T05:06:07","guid":{"rendered":"https:\/\/sozee.ai\/resources\/ai-onlyfans-agency-compliance-standards\/"},"modified":"2026-08-08T06:28:32","modified_gmt":"2026-08-08T06:28:32","slug":"ai-onlyfans-agency-compliance-standards","status":"publish","type":"post","link":"https:\/\/www.sozee.ai\/resources\/ai-onlyfans-agency-compliance-standards\/","title":{"rendered":"AI Content Generation Compliance for OnlyFans Agencies"},"content":{"rendered":"<p><em>Last updated: August 6, 2026<\/em><\/p>\n<h2 id=\"key-takeaways\">Key Takeaways<\/h2>\n<ul>\n<li>AI content generation compliance for OnlyFans agency software in 2026 requires identity verification, consent documentation, disclosure metadata, human moderation, and audit logging under the EU AI Act, U.S. state deepfake statutes, and OnlyFans 2026 AUP.<\/li>\n<li>Every AI-generated asset must include machine-readable disclosure metadata at the file and API layer, including C2PA 2.0 manifests and is_ai_generated flags, to satisfy EU AI Act Article 50.<\/li>\n<li>Consent must be captured per likeness and per use case with tamper-evident records. Blanket terms-of-service acceptance does not constitute valid consent under California AB 602 or the EU AI Act.<\/li>\n<li>High-risk AI systems require human oversight workflows that include a dedicated moderation queue with SLA enforcement. NSFW assets need explicit moderator approval before publish.<\/li>\n<li>Sozee builds verification, consent capture, disclosure metadata, human oversight, prohibited-content detection, audit logging, workspace isolation, content tier gating, and jurisdiction mapping directly into the Cast step so every character enters the generation pipeline with a complete compliance record. <a href=\"https:\/\/app.sozee.ai\/sign-up\" target=\"_blank\">Ship your first audit-ready AI asset with Sozee today<\/a>.<\/li>\n<\/ul>\n<h2>1. Identity and Age Verification for AI OnlyFans Tools<\/h2>\n<p>Every character or likeness used in AI-generated content must be traceable to a verified, consenting adult. Verification that happens after character creation does not satisfy 2026 standards.<\/p>\n<p><strong>Required database fields:<\/strong> <code>creator_id<\/code>, <code>dob_verified<\/code> (ISO 8601 date), <code>id_document_hash<\/code> (SHA-256), <code>verification_provider<\/code>, <code>verification_timestamp<\/code>, <code>verification_status<\/code> (enum: pending | approved | rejected).<\/p>\n<p><strong>API endpoints:<\/strong> <code>POST \/v1\/identity\/verify<\/code>, which submits document and biometric payload. <code>GET \/v1\/identity\/{creator_id}\/status<\/code>, which returns the current verification state. <code>PATCH \/v1\/identity\/{creator_id}\/refresh<\/code>, which triggers re-verification when a document expires.<\/p>\n<p><strong>Moderation workflow:<\/strong> Block character creation until <code>verification_status = approved<\/code>. When the underlying ID document expires, require re-verification to maintain verified status, because an expired document invalidates the compliance record. Log every state change in this workflow to the audit trail with operator ID and timestamp so regulators can reconstruct the verification history for any character.<\/p>\n<p><strong>Jurisdiction note:<\/strong> The <a href=\"https:\/\/ai-act-service-desk.ec.europa.eu\/en\/ai-act\/article-13\" target=\"_blank\" rel=\"noindex nofollow\">EU AI Act Article 13<\/a> requires transparency and provision of information to deployers for high-risk AI systems, while synthetic-content transparency obligations appear in Article 50. U.S. state deepfake statutes, including California AB 602, address nonconsensual synthetic content. Requirements vary by state and by specific context.<\/p>\n<p style=\"text-align:center;\"><strong><a href=\"https:\/\/app.sozee.ai\/sign-up\" target=\"_blank\">Verify every character\u2019s identity at creation and start building your compliant Cast workflow in Sozee.<\/a><\/strong><\/p>\n<h2>2. AI Disclosure Metadata Fields for Creator Platforms<\/h2>\n<p>Asset-level disclosure metadata must travel with every AI-generated file, because platform-only labels do not satisfy EU AI Act Article 50. Every AI-generated asset must carry machine-readable disclosure metadata at both the file and API layer.<\/p>\n<p><strong>Required database fields:<\/strong> <code>asset_id<\/code>, <code>is_ai_generated<\/code> (boolean), <code>generation_model<\/code>, <code>generation_timestamp<\/code>, <code>disclosure_label<\/code> (string, platform-visible), <code>c2pa_manifest_uri<\/code> (link to C2PA 2.0 manifest).<\/p>\n<p><strong>API endpoints:<\/strong> <code>POST \/v1\/assets\/{asset_id}\/metadata<\/code>, which writes disclosure fields at generation. <code>GET \/v1\/assets\/{asset_id}\/metadata<\/code>, which returns the full disclosure record for audit or platform submission.<\/p>\n<p><strong>Moderation workflow:<\/strong> Reject any asset where <code>c2pa_manifest_uri<\/code> is null before publish. Surface <code>disclosure_label<\/code> in the creator-facing UI and in the platform submission payload so disclosure remains visible across the full distribution chain.<\/p>\n<h2>3. Deepfake Consent Software Features<\/h2>\n<p>Valid consent for synthetic likenesses must be specific, documented, and easy to revoke. Consent must be captured per likeness and per use case, then stored in a tamper-evident record.<\/p>\n<p><strong>Required database fields:<\/strong> <code>consent_id<\/code>, <code>creator_id<\/code>, <code>likeness_id<\/code>, <code>consent_scope<\/code> (enum: image | video | audio | all), <code>consent_granted_at<\/code>, <code>consent_revoked_at<\/code> (nullable), <code>consent_document_hash<\/code> (SHA-256 of signed consent record).<\/p>\n<p><strong>API endpoints:<\/strong> <code>POST \/v1\/consent<\/code>, which records a new consent grant. <code>DELETE \/v1\/consent\/{consent_id}<\/code>, which records revocation and propagates a block to the generation pipeline. <code>GET \/v1\/consent\/{creator_id}\/active<\/code>, which returns all active consent scopes.<\/p>\n<p><strong>Moderation workflow:<\/strong> The generation pipeline checks <code>consent_revoked_at<\/code> before every job. Revocation halts in-progress jobs within 60 seconds and flags completed assets for takedown review so the system respects right-to-erasure expectations.<\/p>\n<h2>4. Human Oversight Workflows in Agency Software<\/h2>\n<p>Human oversight turns automated generation into a controlled, reviewable process that satisfies EU AI Act Article 14. High-risk AI systems in agency environments need a dedicated moderation queue instead of post-publish review.<\/p>\n<p><strong>Required database fields:<\/strong> <code>review_queue_id<\/code>, <code>asset_id<\/code>, <code>assigned_moderator_id<\/code>, <code>review_status<\/code> (enum: pending | approved | rejected | escalated), <code>review_timestamp<\/code>, <code>override_reason<\/code> (text, nullable).<\/p>\n<p><strong>API endpoints:<\/strong> <code>GET \/v1\/moderation\/queue<\/code>, which returns pending assets. <code>PATCH \/v1\/moderation\/{review_queue_id}<\/code>, which updates status and logs moderator action. <code>POST \/v1\/moderation\/{review_queue_id}\/escalate<\/code>, which routes items to senior review with a documented reason.<\/p>\n<p><strong>Moderation workflow:<\/strong> All NSFW-classified assets enter the queue before publish. To satisfy the EU AI Act human oversight requirement, moderator approval must occur within a configurable SLA, with four hours as the recommended baseline, so no high-risk content reaches the platform without human review. For assets flagged by the prohibited-content classifier, automated approval is prohibited entirely because these flags indicate potential regulatory violations that require explicit human judgment.<\/p>\n<h2>5. Platform Policy Enforcement for AI Agencies<\/h2>\n<p>OnlyFans 2026 AUP compliance depends on continuous policy checks, not one-time acceptance. Non-compliant accounts face suspension when they cannot prove ongoing adherence.<\/p>\n<p><strong>Required database fields:<\/strong> <code>policy_version<\/code>, <code>policy_accepted_at<\/code>, <code>compliance_score<\/code> (integer 0\u2013100), <code>last_audit_timestamp<\/code>, <code>audit_result<\/code> (enum: pass | fail | pending).<\/p>\n<p><strong>API endpoints:<\/strong> <code>GET \/v1\/compliance\/report\/{workspace_id}<\/code>, which generates an exportable compliance report. <code>POST \/v1\/compliance\/audit<\/code>, which triggers an on-demand audit against the current policy version. <code>PATCH \/v1\/compliance\/policy-accept<\/code>, which records policy version acceptance.<\/p>\n<p><strong>Moderation workflow:<\/strong> An automated daily audit compares workspace assets against current policy rules. Assets that fail the audit are quarantined and flagged for human review before any platform submission.<\/p>\n<p style=\"text-align:center;\"><strong><a href=\"https:\/\/app.sozee.ai\/sign-up\" target=\"_blank\">Generate your first OnlyFans AUP compliance report in Sozee without manual audits.<\/a><\/strong><\/p>\n<h2>6. Prohibited Content Detection in AI Pipelines<\/h2>\n<p>Prohibited-content detection protects agencies from high-risk outputs before they reach human moderators. Every generated asset must pass through a classifier, and those results must be logged and auditable.<\/p>\n<p><strong>Required database fields:<\/strong> <code>classifier_run_id<\/code>, <code>asset_id<\/code>, <code>classifier_version<\/code>, <code>prohibited_flags<\/code> (JSON array of triggered categories), <code>confidence_score<\/code> (float), <code>classifier_timestamp<\/code>.<\/p>\n<p><strong>API endpoints:<\/strong> <code>POST \/v1\/classifier\/run<\/code>, which submits an asset for classification. <code>GET \/v1\/classifier\/{classifier_run_id}\/result<\/code>, which returns flags and confidence scores.<\/p>\n<p><strong>Moderation workflow:<\/strong> Assets with any prohibited flag above the configured confidence threshold are automatically rejected and logged. Document threshold configuration in the compliance report so reviewers understand the agency\u2019s risk posture.<\/p>\n<h2>7. Audit Logging and Retention Requirements<\/h2>\n<p>Comprehensive audit logs give regulators a full picture of how your system behaves over time. The EU AI Act Article 12 requires automatic logging for high-risk AI systems, and Articles 19 and 26(6) require providers and deployers to retain those logs for at least six months.<\/p>\n<p><strong>Required database fields:<\/strong> <code>log_id<\/code>, <code>event_type<\/code>, <code>actor_id<\/code>, <code>resource_id<\/code>, <code>resource_type<\/code>, <code>event_timestamp<\/code>, <code>ip_address<\/code>, <code>log_hash<\/code> (SHA-256 chained hash for tamper evidence).<\/p>\n<p><strong>API endpoints:<\/strong> <code>GET \/v1\/audit\/logs<\/code>, which provides paginated log retrieval with filters by event type, actor, and date range. <code>POST \/v1\/audit\/export<\/code>, which generates a signed export for regulatory submission.<\/p>\n<p><strong>Moderation workflow:<\/strong> Logs are append-only. Any attempt to modify a log entry triggers an integrity alert and notifies the compliance lead.<\/p>\n<h2>8. Workspace Isolation for Multi\u2011Creator Agencies<\/h2>\n<p>Strict workspace isolation prevents cross-account data leakage and supports GDPR and OnlyFans AUP requirements. Agencies that manage multiple creators must keep each workspace logically and programmatically separate.<\/p>\n<p><strong>Required database fields:<\/strong> <code>workspace_id<\/code>, <code>owner_account_id<\/code>, <code>isolation_level<\/code> (enum: strict | standard), <code>created_at<\/code>, <code>data_residency_region<\/code>.<\/p>\n<p><strong>API endpoints:<\/strong> <code>POST \/v1\/workspaces<\/code>, which creates an isolated workspace. <code>GET \/v1\/workspaces\/{workspace_id}\/members<\/code>, which returns an access-controlled member list. <code>DELETE \/v1\/workspaces\/{workspace_id}\/data<\/code>, which triggers GDPR-compliant data erasure.<\/p>\n<p><strong>Moderation workflow:<\/strong> Scope all API calls to a single <code>workspace_id<\/code>. Cross-workspace queries return 403. Log erasure requests and confirm completion within 30 days.<\/p>\n<h2>9. SFW-to-NSFW Content Gating Controls<\/h2>\n<p>Server-side gating keeps NSFW generation behind explicit approvals, even when users access APIs directly. Content pipelines that support an SFW-to-NSFW arc must enforce gating at the generation layer.<\/p>\n<p><strong>Required database fields:<\/strong> <code>content_tier<\/code> (enum: sfw | suggestive | nsfw), <code>tier_unlock_verified<\/code> (boolean), <code>tier_unlock_timestamp<\/code>, <code>tier_unlock_operator_id<\/code>.<\/p>\n<p><strong>API endpoints:<\/strong> <code>POST \/v1\/content\/tier-unlock<\/code>, which records operator approval to unlock NSFW generation for a workspace. <code>GET \/v1\/content\/{asset_id}\/tier<\/code>, which returns the current content tier classification.<\/p>\n<p><strong>Moderation workflow:<\/strong> Block NSFW generation until <code>tier_unlock_verified = true<\/code> and log the unlocking operator\u2019s identity. Re-evaluate tier classification with the classifier on every generation job.<\/p>\n<h2>10. Cross-Jurisdiction Compliance Mapping<\/h2>\n<p>Jurisdiction-aware rules keep global agencies aligned with the strictest applicable standards. Software deployed across the EU, U.S., and UK must map each workspace to the relevant regulatory regime and apply overlapping requirements conservatively.<\/p>\n<p><strong>Required database fields:<\/strong> <code>jurisdiction_code<\/code> (ISO 3166-1 alpha-2), <code>applicable_regulations<\/code> (JSON array), <code>strictest_rule_set<\/code> (computed field), <code>last_regulation_sync<\/code>.<\/p>\n<p><strong>API endpoints:<\/strong> <code>GET \/v1\/compliance\/jurisdiction\/{workspace_id}<\/code>, which returns the applicable rule set. <code>POST \/v1\/compliance\/jurisdiction\/sync<\/code>, which pulls the latest regulation updates from the compliance rules engine.<\/p>\n<p><strong>Moderation workflow:<\/strong> On workspace creation, the system assigns <code>jurisdiction_code<\/code> based on operator billing address and creator IP geolocation. When jurisdictions conflict, the system defaults to the strictest applicable rule. Regulation sync runs nightly.<\/p>\n<h2>How Sozee Embeds This Checklist into Agency Workflows<\/h2>\n<p>The 10-item checklist above becomes practical only when compliance lives at character creation instead of as a post-generation patch. Sozee follows this approach by integrating verification, consent, disclosure, and the remaining controls directly into the Cast step.<\/p>\n<p>Compliance functions as an architecture decision in Sozee. Every character enters the pipeline with a complete compliance record, and each stage of the workflow enforces the relevant rule set before content moves forward.<\/p>\n<p>Compliance is not a feature that you bolt on after launch. The table below shows how each of the ten requirements maps to a specific enforcement point in Sozee\u2019s pipeline. Verification, consent, disclosure, and human review all occur before or during generation, not after assets are already live, which aligns with 2026 regulatory expectations.<\/p>\n<table>\n<thead>\n<tr>\n<th>Checklist Item<\/th>\n<th>Required Technical Component<\/th>\n<th>Sozee Capability<\/th>\n<th>Enforcement Point<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>1. Identity &amp; Age Verification<\/td>\n<td><code>verification_status<\/code> gate on character creation<\/td>\n<td>Built-in ID verification at Cast step, which blocks generation until approval<\/td>\n<td>Character creation<\/td>\n<\/tr>\n<tr>\n<td>2. AI Disclosure Metadata<\/td>\n<td>C2PA 2.0 manifest plus <code>is_ai_generated<\/code> field<\/td>\n<td>Auto-written disclosure metadata on every generated asset<\/td>\n<td>Generation pipeline<\/td>\n<\/tr>\n<tr>\n<td>3. Deepfake Consent<\/td>\n<td>Per-likeness, per-scope consent record<\/td>\n<td>Consent capture and revocation API integrated at character setup<\/td>\n<td>Character creation and generation<\/td>\n<\/tr>\n<tr>\n<td>4. Human Oversight<\/td>\n<td>Moderation queue with SLA enforcement<\/td>\n<td>Configurable review queue where NSFW assets require moderator approval before publish<\/td>\n<td>Pre-publish<\/td>\n<\/tr>\n<tr>\n<td>5. Platform Policy Enforcement<\/td>\n<td>Exportable compliance report plus daily audit<\/td>\n<td>On-demand compliance report generation for OnlyFans AUP submission<\/td>\n<td>Ongoing and on-demand<\/td>\n<\/tr>\n<tr>\n<td>6. Prohibited Content Detection<\/td>\n<td>Classifier with logged confidence scores<\/td>\n<td>Automated classifier runs on every asset and quarantines flags before queue entry<\/td>\n<td>Post-generation, pre-queue<\/td>\n<\/tr>\n<tr>\n<td>7. Audit Logging<\/td>\n<td>Append-only, chained-hash log store<\/td>\n<td>Full audit trail across all events with signed export for regulatory submission<\/td>\n<td>All pipeline stages<\/td>\n<\/tr>\n<tr>\n<td>8. Workspace Isolation<\/td>\n<td>Workspace-scoped API with erasure endpoint<\/td>\n<td>Fully isolated workspaces per client with no cross-workspace leakage<\/td>\n<td>Account and data layer<\/td>\n<\/tr>\n<tr>\n<td>9. Content Tier Gating<\/td>\n<td>Server-side tier-unlock enforcement<\/td>\n<td>SFW-to-NSFW arc with operator-approved tier unlock and API-level bypass blocking<\/td>\n<td>Generation pipeline<\/td>\n<\/tr>\n<tr>\n<td>10. Jurisdiction Mapping<\/td>\n<td>Regulation sync engine plus strictest-rule default<\/td>\n<td>Automatic jurisdiction assignment with nightly regulation sync and strictest-rule conflict handling<\/td>\n<td>Workspace creation and ongoing<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p style=\"text-align:center;\"><strong><a href=\"https:\/\/app.sozee.ai\/sign-up\" target=\"_blank\">Go live with a compliant AI content pipeline in Sozee before your competitors catch up.<\/a><\/strong><\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Difference between platform-level AI disclosure and asset-level metadata<\/h3>\n<p>Platform-level disclosure is a label that the hosting platform applies, such as a banner or tag, after content is uploaded. Asset-level disclosure metadata lives in the file itself and in the API record at the moment of generation, using standards like C2PA 2.0. EU AI Act Article 50 requires asset-level disclosure so the signal travels with the content wherever it is distributed.<\/p>\n<p>Platform labels can be stripped or lost during re-uploads. Embedded metadata persists across copies. Agency software should write disclosure fields to the database and the file at generation time instead of relying on platforms to apply them later.<\/p>\n<h3>Impact of consent revocation on already-published AI content<\/h3>\n<p>Consent revocation must ripple through the full pipeline. The generation layer blocks new jobs that use the revoked likeness immediately. In-progress jobs halt within a defined SLA, and completed assets are flagged for takedown review.<\/p>\n<p>Published assets do not disappear automatically. Agency software must surface a takedown workflow for the compliance lead, who then acts on the flagged items. Failure to act within a reasonable timeframe creates legal exposure under U.S. state deepfake statutes and GDPR Article 17 right-to-erasure obligations. The consent record logs the revocation timestamp and the follow-up actions.<\/p>\n<h3>Meaning of \u201chuman oversight\u201d for agencies at scale<\/h3>\n<p>Human oversight under EU AI Act Article 14 means a qualified operator can monitor outputs, intervene before publication, and halt the system. For an agency that runs dozens of creator accounts, this translates into a staffed moderation queue.<\/p>\n<p>Every NSFW-classified asset requires explicit moderator approval before submission to any platform. The queue operates within a documented SLA, and every approval or rejection is logged with moderator ID and timestamp. Automated approval of flagged assets remains non-compliant. Agencies should assign dedicated compliance leads per workspace tier and configure escalation paths for assets that exceed the prohibited-content classifier\u2019s confidence threshold.<\/p>\n<h3>Applicability of the EU AI Act to agencies outside the EU<\/h3>\n<p>The EU AI Act applies whenever AI system outputs are used within the EU, regardless of where the provider is incorporated. A U.S. or UK agency that serves EU-based subscribers falls within scope when AI-generated content reaches those subscribers.<\/p>\n<p>Jurisdiction mapping therefore depends on end-user location, not only on the operator\u2019s billing address. Agencies should treat EU AI Act requirements as a baseline and then layer U.S. state deepfake statutes for creators with U.S. audiences.<\/p>\n<h3>OnlyFans 2026 AUP changes that affect AI content agencies<\/h3>\n<p>The OnlyFans 2026 AUP requires accounts using AI-generated content to prove, at account creation and on audit request, that all synthetic likenesses link to verified identity records, documented consent, and machine-readable disclosure metadata. Accounts that cannot produce an exportable compliance report on demand face immediate suspension.<\/p>\n<p>The AUP also prohibits AI-generated content that depicts any person without documented consent, whether the likeness is photorealistic or stylized. Agencies must ensure their software can generate a workspace-scoped compliance report in a format acceptable to the OnlyFans trust and safety team.<\/p>\n<h2>Conclusion<\/h2>\n<p>The 10-item checklist covering identity verification, disclosure metadata, deepfake consent, human oversight, platform policy enforcement, prohibited content detection, audit logging, workspace isolation, content tier gating, and jurisdiction mapping defines the minimum technical architecture for OnlyFans agency software in 2026. The features table above connects each requirement to a concrete Sozee capability so product teams can translate regulations into roadmap items.<\/p>\n<p>Manual or post-generation compliance cannot keep pace with the EU AI Act, U.S. deepfake statutes, or the OnlyFans 2026 AUP. These frameworks expect verification, consent, and disclosure to exist at character creation and to remain enforceable throughout the pipeline. Sozee\u2019s Cast-step integration delivers that model so every asset your agency generates is audit-ready from the first frame.<\/p>\n<p style=\"text-align:center;\"><strong><a href=\"https:\/\/app.sozee.ai\/sign-up\" target=\"_blank\">Ship your first audit-ready AI content workflow in Sozee now.<\/a><\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Meet 2026 AI content compliance for OnlyFans agencies. Sozee builds in verification, consent, disclosure &#038; audit tools \u2014 stay compliant effortlessly.<\/p>\n","protected":false},"author":2,"featured_media":20249,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,4,12],"tags":[14],"class_list":["post-17667","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agencies","category-creator-platforms","category-legal-safety","tag-onlyfans"],"_links":{"self":[{"href":"https:\/\/www.sozee.ai\/resources\/wp-json\/wp\/v2\/posts\/17667","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sozee.ai\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sozee.ai\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sozee.ai\/resources\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sozee.ai\/resources\/wp-json\/wp\/v2\/comments?post=17667"}],"version-history":[{"count":1,"href":"https:\/\/www.sozee.ai\/resources\/wp-json\/wp\/v2\/posts\/17667\/revisions"}],"predecessor-version":[{"id":20250,"href":"https:\/\/www.sozee.ai\/resources\/wp-json\/wp\/v2\/posts\/17667\/revisions\/20250"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.sozee.ai\/resources\/wp-json\/wp\/v2\/media\/20249"}],"wp:attachment":[{"href":"https:\/\/www.sozee.ai\/resources\/wp-json\/wp\/v2\/media?parent=17667"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sozee.ai\/resources\/wp-json\/wp\/v2\/categories?post=17667"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sozee.ai\/resources\/wp-json\/wp\/v2\/tags?post=17667"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}