{"id":43285,"date":"2026-11-17T09:06:01","date_gmt":"2026-11-17T03:36:01","guid":{"rendered":"https:\/\/www.aspiresys.com\/blog\/?p=43285"},"modified":"2026-11-18T09:07:07","modified_gmt":"2026-11-18T03:37:07","slug":"how-should-you-compare-ai-integration-options-for-oracle-fusion-and-ebs","status":"publish","type":"post","link":"https:\/\/www.aspiresys.com\/blog\/oracle\/enterprise-business-applications\/how-should-you-compare-ai-integration-options-for-oracle-fusion-and-ebs\/","title":{"rendered":"How should you compare AI integration options for Oracle Fusion and EBS?"},"content":{"rendered":"\n<p>Oracle Fusion Cloud Applications centralize AI capabilities within cloud business workflows, while Oracle E-Business Suite usually connects to AI through custom integration architecture, often using <a href=\"https:\/\/www.aspiresys.com\/oracle\/oracle-cloud-infrastructure?utm_source=vendor_blog&amp;utm_medium=blog-post&amp;utm_campaign=oracle_content_marketing\" target=\"_blank\" rel=\"noopener\" title=\"\">Oracle Cloud Infrastructure<\/a>; the right choice depends on ownership, governance, process fit, and long-term operating complexity.\u00a0<\/p>\n\n\n\n<p>The important distinction is not simply native versus custom. It is whether the organization wants AI capabilities embedded in an application operating model or prefers to preserve EBS while owning the APIs, data pipelines, retrieval layer, identity controls, monitoring, and change management around an AI service.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What decision does an Oracle team need to make first?<\/strong>&nbsp;<\/h2>\n\n\n\n<p>Oracle Fusion Cloud Applications provide an application-centered path to AI, whereas Oracle E-Business Suite provides a preservation path that may need additional integration services. This distinction determines who owns provisioning, authorization, prompt governance, failover, observability, and release coordination. The business outcome depends on selecting an operating model that the organization can sustain.&nbsp;<\/p>\n\n\n\n<p>Start with the business process rather than the model. A procurement summary, service-desk assistant, or finance explanation has different data boundaries and approval requirements from an autonomous transaction workflow. Map the user, decision, source data, permitted action, human review point, and audit record before comparing products.&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>\u00a0Choose native Fusion AI when:\u00a0<\/strong> the process already <a href=\"https:\/\/www.aspiresys.com\/revolutionizing-enterprise-management-power-of-oracle-fusion-erp-solutions\/?utm_source=vendor_blog&amp;utm_medium=blog-post&amp;utm_campaign=oracle_content_marketing\" target=\"_blank\" rel=\"noopener\" title=\"\">fits Fusion workflows<\/a> and the organization values application-aligned administration.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>\u00a0Choose custom EBS integration when:\u00a0<\/strong> the existing EBS process remains strategically important and the AI use case can be isolated behind controlled interfaces.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>\u00a0Assess migration when:\u00a0<\/strong> AI is one part of a broader cloud, process, data, and integration modernization program.\u00a0<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Why does a feature-by-feature comparison often mislead buyers?<\/strong>&nbsp;<\/h2>\n\n\n\n<p>A feature list compares visible functions but hides operating responsibility. Native Fusion AI and a custom Oracle E-Business Suite solution differ in data access, release management, integration testing, security design, support boundaries, and the skills needed after launch.&nbsp;<\/p>\n\n\n\n<p>Feature parity is also an unreliable <a href=\"https:\/\/www.aspiresys.com\/blog\/oracle\/erp-implementation\/generative-ai-in-erp-beyond-the-hype-to-enterprise-reality?utm_source=vendor_blog&amp;utm_medium=blog-post&amp;utm_campaign=oracle_content_marketing\" target=\"_blank\" rel=\"noopener\" title=\"\">measure for generative AI<\/a>. A chatbot that answers questions from documents is not equivalent to an assistant that understands application roles, workflow state, transaction context, and approved actions. The evaluation should therefore compare the complete control plane, not only the interface shown to users.\u00a0<\/p>\n\n\n\n<p>A total-cost-of-ownership model should include implementation, integration, environment management, identity administration, data preparation, prompt and retrieval evaluation, incident response, audit support, and changes caused by ERP releases. This exposes costs that a license comparison leaves outside the frame.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Which criteria separate native Fusion AI from custom EBS integration?<\/strong>&nbsp;<\/h2>\n\n\n\n<p>Native Fusion AI aligns AI capabilities with the <a href=\"https:\/\/www.aspiresys.com\/future-of-erp-how-oracle-fusion-changing-the-game\/?utm_source=vendor_blog&amp;utm_medium=blog-post&amp;utm_campaign=oracle_content_marketing\" target=\"_blank\" rel=\"noopener\" title=\"\">Fusion application model<\/a>, while custom EBS integration assembles a separate service chain around Oracle E-Business Suite. The useful comparison covers control, coupling, extensibility, and operational ownership rather than feature count alone.\u00a0<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Feature<\/strong>&nbsp;<\/td><td><strong>New Approach: Native Fusion AI<\/strong>&nbsp;<\/td><td><strong>Traditional Approach: Custom AI for EBS<\/strong>&nbsp;<\/td><\/tr><tr><td>Core mechanism&nbsp;<\/td><td>AI capability is presented through Fusion application workflows and supported extension points.&nbsp;<\/td><td>AI connects to EBS through APIs, integration services, data stores, retrieval components, and application interfaces.&nbsp;<\/td><\/tr><tr><td>Data context&nbsp;<\/td><td>Application context and permissions are closer to the workflow being assisted.&nbsp;<\/td><td>The integration team defines which transactional records, documents, and metadata enter the AI context.&nbsp;<\/td><\/tr><tr><td>Operational ownership&nbsp;<\/td><td>Oracle manages more of the underlying application service boundary.&nbsp;<\/td><td>The customer or implementation partner owns orchestration, monitoring, incident handling, and component coordination.&nbsp;<\/td><\/tr><tr><td>Customization&nbsp;<\/td><td>Customization follows available Fusion configuration and extension patterns.&nbsp;<\/td><td>Custom prompts, retrieval logic, interfaces, and business rules can address a narrower EBS use case.&nbsp;<\/td><\/tr><tr><td>Governance&nbsp;<\/td><td>Governance is organized around Fusion roles, application data, and cloud controls.&nbsp;<\/td><td>Governance spans EBS, OCI, identity, data movement, model access, retrieval sources, and generated outputs.&nbsp;<\/td><\/tr><tr><td>Change management&nbsp;<\/td><td>Application releases and supported capabilities shape the change process.&nbsp;<\/td><td>ERP changes can affect APIs, schemas, retrieval content, orchestration, tests, and user interfaces.&nbsp;<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Oracle Cloud Infrastructure is most useful in the EBS path when it provides a controlled boundary for integration, identity, storage, model access, and observability. It does not remove the need to design data contracts or decide which generated actions require human approval.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How should teams evaluate security, governance, and data control?<\/strong>&nbsp;<\/h2>\n\n\n\n<p>Security architecture determines whether an AI integration is usable in production. Oracle Fusion Cloud Applications place more of the application boundary inside the cloud service, whereas an OCI-based EBS design distributes responsibility across application permissions, network paths, identity policies, retrieval stores, model endpoints, logs, and user interfaces.&nbsp;<\/p>\n\n\n\n<p>Evaluate the <a href=\"https:\/\/www.aspiresys.com\/blog\/oracle\/erp-implementation\/ai-labs-to-erp-operations-what-it-takes-to-operationalize-ai?utm_source=vendor_blog&amp;utm_medium=blog-post&amp;utm_campaign=oracle_content_marketing\" target=\"_blank\" rel=\"noopener\" title=\"\">complete data journey<\/a>: source extraction, transformation, transport, indexing, retrieval, prompt assembly, model response, presentation, retention, and deletion. For each stage, assign a data owner and define whether the output is advisory, approval-supporting, or capable of initiating an action.\u00a0<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>How can an organization score AI readiness before choosing an architecture?<\/strong>&nbsp;<\/h3>\n\n\n\n<p>The following is a practical evaluation rubric, not a description of <a href=\"https:\/\/www.aspiresys.com\/oracle\/enterprise-ai-platform-oracle-erp-optimization?utm_source=vendor_blog&amp;utm_medium=blog-post&amp;utm_campaign=oracle_content_marketing\" target=\"_blank\" rel=\"noopener\" title=\"\">how an AI model operates<\/a>. A failed item indicates a design dependency that should be resolved before expanding the use case.\u00a0<\/p>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li><strong>\u00a0Entity consistency:\u00a0<\/strong> As a working threshold, entity-naming deviation above 10% signals high risk, while deviation below 5% is a pass.\u00a0<strong> Action:\u00a0<\/strong> align names for suppliers, customers, legal entities, accounts, products, and business units across source systems.\u00a0<\/li>\n<\/ol>\n\n\n\n<ol start=\"2\" class=\"wp-block-list\">\n<li><strong>\u00a0Data provenance validation:\u00a0<\/strong> Treat missing source ownership, timestamps, lineage, or retention rules as a fail.\u00a0<strong> Action:\u00a0<\/strong> record the source, owner, permitted use, freshness expectation, and deletion path for every retrieval collection.\u00a0<\/li>\n<\/ol>\n\n\n\n<ol start=\"3\" class=\"wp-block-list\">\n<li><strong>\u00a0Contextual embedding score:\u00a0<\/strong> As a practical heuristic, a score below 60% indicates low relevance and a score above 70% is a pass.\u00a0<strong> Action:\u00a0<\/strong> test representative questions and improve chunking, metadata, terminology, and source selection when relevance is low.\u00a0<\/li>\n<\/ol>\n\n\n\n<ol start=\"4\" class=\"wp-block-list\">\n<li><strong>\u00a0Knowledge graph alignment:\u00a0<\/strong> Treat unresolved relationships between business entities as a fail for use cases that depend on organizational context.\u00a0<strong> Action:\u00a0<\/strong> map relationships such as supplier-to-site, account-to-ledger, and employee-to-approval role before retrieval design.\u00a0<\/li>\n<\/ol>\n\n\n\n<ol start=\"5\" class=\"wp-block-list\">\n<li><strong>\u00a0Structured data validation:\u00a0<\/strong> Treat inconsistent schemas, undocumented fields, or ambiguous status values as a fail.\u00a0<strong> Action:\u00a0<\/strong> document interface contracts, validate payloads, and separate source facts from generated explanations.\u00a0<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What does a practical migration and integration roadmap look like?<\/strong>&nbsp;<\/h2>\n\n\n\n<p>An <a href=\"https:\/\/www.aspiresys.com\/oracle-erp-analytics-ai-automation\/?utm_source=vendor_blog&amp;utm_medium=blog-post&amp;utm_campaign=oracle_content_marketing\" target=\"_blank\" rel=\"noopener\" title=\"\">AI roadmap for Oracle E-Business Suite<\/a> should move from a bounded information task to controlled workflow assistance, not from a model demonstration directly to autonomous execution. Oracle Cloud Infrastructure can host integration components, but the roadmap still needs ownership for data, security, evaluation, and operations.\u00a0<\/p>\n\n\n\n<ol start=\"6\" class=\"wp-block-list\">\n<li><strong>\u00a0Define the decision:\u00a0<\/strong> identify the user question or workflow decision, the authoritative sources, the prohibited outputs, and the human approval point.\u00a0<\/li>\n<\/ol>\n\n\n\n<ol start=\"7\" class=\"wp-block-list\">\n<li><strong>\u00a0Establish the integration boundary:\u00a0<\/strong> select APIs, extracts, documents, identity paths, network controls, and the interface through which users receive results.\u00a0<\/li>\n<\/ol>\n\n\n\n<ol start=\"8\" class=\"wp-block-list\">\n<li><strong>\u00a0Evaluate the response:\u00a0<\/strong> test retrieval relevance, factual grounding, access enforcement, refusal behavior, auditability, and performance against representative work.\u00a0<\/li>\n<\/ol>\n\n\n\n<ol start=\"9\" class=\"wp-block-list\">\n<li><strong>\u00a0Operate the service:\u00a0<\/strong> assign owners for source changes, prompt changes, model changes, incident response, access reviews, and regression testing after EBS changes.\u00a0<\/li>\n<\/ol>\n\n\n\n<p>For Oracle Fusion Cloud Applications, the same <a href=\"https:\/\/www.aspiresys.com\/oracle\/oracle-fusion-migration-and-implementation?utm_source=vendor_blog&amp;utm_medium=blog-post&amp;utm_campaign=oracle_content_marketing\" target=\"_blank\" rel=\"noopener\" title=\"\">roadmap focuses more on process fit<\/a>, supported configuration, role design, workflow placement, and the boundaries of available AI capabilities. For EBS, the roadmap carries additional architecture decisions because the AI layer is outside the core application experience.\u00a0<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What are the trade-offs between Fusion AI and bolt-on EBS architecture?<\/strong>&nbsp;<\/h2>\n\n\n\n<p>Native Fusion AI reduces the number of independently operated integration components, while bolt-on EBS architecture preserves the existing ERP foundation and permits targeted customization. Neither path removes governance work; each places that work in a different operating boundary.&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>\u00a0Not suitable when:\u00a0<\/strong> native Fusion AI does not fit the required process, data residency model, approval design, or extension boundary.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>\u00a0Not suitable when:\u00a0<\/strong> custom EBS integration lacks accountable owners for identity, data quality, retrieval evaluation, monitoring, and release testing.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>\u00a0Consideration:\u00a0<\/strong> custom integration creates an ongoing maintenance burden across APIs, data contracts, prompts, retrieval sources, model access, logs, and user interfaces.\u00a0<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>\u00a0Trade-off vs alternative:\u00a0<\/strong> preserving EBS can avoid an <a href=\"https:\/\/www.aspiresys.com\/oracle-cloud-erp-vs-oracle-ebs\/?utm_source=vendor_blog&amp;utm_medium=blog-post&amp;utm_campaign=oracle_content_marketing\" target=\"_blank\" rel=\"noopener\" title=\"\">immediate ERP migration<\/a>, but it exchanges migration work for continuing integration complexity and separate AI governance.\u00a0<\/li>\n<\/ul>\n\n\n\n<p>The practical decision is therefore a portfolio decision. A narrow, read-only assistant may fit a controlled EBS integration, while process-wide automation may justify assessing Fusion migration alongside broader modernization objectives.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How should an organization choose between Fusion AI and custom EBS integration?<\/strong>&nbsp;<\/h2>\n\n\n\n<p>Oracle Fusion Cloud Applications are the stronger alignment choice when the target process is already moving to Fusion and the organization prefers a supported <a href=\"https:\/\/www.aspiresys.com\/blog\/oracle\/erp-implementation\/from-systems-of-record-to-systems-of-judgment-how-enterprise-ai-is-redefining-the-future-of-erp?utm_source=vendor_blog&amp;utm_medium=blog-post&amp;utm_campaign=oracle_content_marketing\" target=\"_blank\" rel=\"noopener\" title=\"\">application-centered operating model<\/a>. Custom Oracle E-Business Suite integration is more defensible when the EBS process remains essential, the use case has a clear boundary, and the organization accepts ownership of the surrounding platform.\u00a0<\/p>\n\n\n\n<p>Use a decision record that states the process, data sources, control requirements, integration boundary, accountable team, expected change burden, and reason an alternative was rejected. This record prevents an AI proof of concept from becoming an unmanaged production dependency.&nbsp;<\/p>\n\n\n\n<p>Use the comparison table and readiness rubric to <a href=\"https:\/\/www.aspiresys.com\/oracle-implementation-consulting-partner?utm_source=vendor_blog&amp;utm_medium=blog-post&amp;utm_campaign=oracle_content_marketing\" target=\"_blank\" rel=\"noopener\" title=\"\">structure an architecture workshop<\/a> with ERP owners, security, integration engineering, data governance, and business process leaders.\u00a0<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Frequently Asked Questions<\/strong>&nbsp;<\/h3>\n\n\n\n<p>Oracle Fusion AI and custom Oracle E-Business Suite integration answer different architecture questions. The following answers address cost, implementation, governance, maintenance, and migration decisions in standalone terms.&nbsp;<\/p>\n\n\n\n<div data-schema-only=\"false\" class=\"wp-block-aioseo-faq\"><h3 class=\"aioseo-faq-block-question\"><strong>How does total cost of ownership differ between Fusion AI and EBS integration?<\/strong>\u00a0<\/h3><div class=\"aioseo-faq-block-answer\">\n<p>Oracle Fusion Cloud Applications generally concentrates AI capabilities inside a managed application environment, whereas Oracle E-Business Suite integrations add architecture, monitoring, security controls, model operations, and specialist maintenance. The correct comparison includes recurring operational work, not only license or implementation costs.\u00a0<\/p>\n<\/div><\/div>\n\n\n\n<div data-schema-only=\"false\" class=\"wp-block-aioseo-faq\"><h3 class=\"aioseo-faq-block-question\"><strong>How do pre-built Fusion AI agents compare with a custom RAG chatbot for EBS?<\/strong>\u00a0<\/h3><div class=\"aioseo-faq-block-answer\">\n<p>Pre-built Fusion AI agents align with workflows and data exposed by Oracle Fusion Cloud Applications. A custom RAG chatbot for Oracle E-Business Suite can address a narrower knowledge need, but the team owns document ingestion, retrieval quality, access control, prompt design, evaluation, and ongoing content maintenance.\u00a0<\/p>\n<\/div><\/div>\n\n\n\n<div data-schema-only=\"false\" class=\"wp-block-aioseo-faq\"><h3 class=\"aioseo-faq-block-question\"><strong>What technical prerequisites support an OCI-based EBS integration?<\/strong>\u00a0<\/h3><div class=\"aioseo-faq-block-answer\">\n<p>An OCI-based integration needs an approved connectivity pattern, stable access to EBS data, an identity model, logging, monitoring, data classification, and an interface for returning approved outputs to users. The exact services depend on whether the use case reads transactional data, documents, or both.\u00a0<\/p>\n<\/div><\/div>\n\n\n\n<div data-schema-only=\"false\" class=\"wp-block-aioseo-faq\"><h3 class=\"aioseo-faq-block-question\"><strong>How do security and governance models differ?<\/strong>\u00a0<\/h3><div class=\"aioseo-faq-block-answer\">\n<p>Native Fusion AI keeps governance within the application and cloud control model available for Fusion Cloud Applications. A custom OCI-based integration with Oracle E-Business Suite creates more design responsibility for identity, authorization, data movement, prompt content, retention, audit records, and separation between retrieved context and generated text.\u00a0<\/p>\n<\/div><\/div>\n\n\n\n<div data-schema-only=\"false\" class=\"wp-block-aioseo-faq\"><h3 class=\"aioseo-faq-block-question\"><strong>What skills are needed to maintain each approach?<\/strong>\u00a0<\/h3><div class=\"aioseo-faq-block-answer\">\n<p>Fusion AI administration emphasizes Oracle application configuration, workflow ownership, access governance, and vendor-supported features. Custom EBS integration adds skills in OCI architecture, integration engineering, retrieval systems, evaluation, observability, security engineering, and lifecycle management for prompts and knowledge sources.\u00a0<\/p>\n<\/div><\/div>\n\n\n\n<div data-schema-only=\"false\" class=\"wp-block-aioseo-faq\"><h3 class=\"aioseo-faq-block-question\"><strong>When does migrating from EBS to Fusion make sense for AI and automation?<\/strong>\u00a0<\/h3><div class=\"aioseo-faq-block-answer\">\n<p>Migration deserves consideration when AI and automation are part of a wider need to <a href=\"https:\/\/www.aspiresys.com\/oracle\/oracle-fusion-migration-and-implementation?utm_source=vendor_blog&amp;utm_medium=blog-post&amp;utm_campaign=oracle_content_marketing\" target=\"_blank\" rel=\"noopener\" title=\"\">modernize processes, reduce custom integration boundaries<\/a>, and adopt cloud application capabilities. AI alone is not a sufficient business case; process fit, data readiness, regulatory constraints, and migration effort also determine the decision.\u00a0<\/p>\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Oracle Fusion Cloud Applications centralize AI capabilities within cloud business workflows, while Oracle E-Business Suite usually connects to AI through&#8230;<\/p>\n","protected":false},"author":163,"featured_media":43287,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4793],"tags":[6357,5806,2261,6301,5355,6358,6264,6355,3203,6354,6353,6356],"practice_industry":[4526],"coauthors":[2391],"class_list":["post-43285","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-enterprise-business-applications","tag-ai-integration-strategy","tag-enterprise-ai-security","tag-erp-automation","tag-erp-data-governance","tag-erp-modernization","tag-fusion-ai-agents","tag-oci-generative-ai","tag-on-premise-erp","tag-oracle-cloud-migration","tag-oracle-ebs-integration","tag-oracle-fusion-ai","tag-rag-chatbot-architecture","practice_industry-oracle"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.aspiresys.com\/blog\/wp-json\/wp\/v2\/posts\/43285","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.aspiresys.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.aspiresys.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.aspiresys.com\/blog\/wp-json\/wp\/v2\/users\/163"}],"replies":[{"embeddable":true,"href":"https:\/\/www.aspiresys.com\/blog\/wp-json\/wp\/v2\/comments?post=43285"}],"version-history":[{"count":1,"href":"https:\/\/www.aspiresys.com\/blog\/wp-json\/wp\/v2\/posts\/43285\/revisions"}],"predecessor-version":[{"id":43288,"href":"https:\/\/www.aspiresys.com\/blog\/wp-json\/wp\/v2\/posts\/43285\/revisions\/43288"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.aspiresys.com\/blog\/wp-json\/wp\/v2\/media\/43287"}],"wp:attachment":[{"href":"https:\/\/www.aspiresys.com\/blog\/wp-json\/wp\/v2\/media?parent=43285"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.aspiresys.com\/blog\/wp-json\/wp\/v2\/categories?post=43285"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.aspiresys.com\/blog\/wp-json\/wp\/v2\/tags?post=43285"},{"taxonomy":"practice_industry","embeddable":true,"href":"https:\/\/www.aspiresys.com\/blog\/wp-json\/wp\/v2\/practice_industry?post=43285"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.aspiresys.com\/blog\/wp-json\/wp\/v2\/coauthors?post=43285"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}