{"id":489416,"date":"2026-08-01T15:42:11","date_gmt":"2026-08-01T15:42:11","guid":{"rendered":"https:\/\/savepearlharbor.com\/?p=489416"},"modified":"-0001-11-30T00:00:00","modified_gmt":"-0001-11-29T21:00:00","slug":"","status":"publish","type":"post","link":"https:\/\/savepearlharbor.com\/?p=489416","title":{"rendered":"OpenAI Codex Ambassadors: How the Developer Community Program Works"},"content":{"rendered":"<div xmlns=\"http:\/\/www.w3.org\/1999\/xhtml\">\n<p>Developer tools are often introduced through documentation, release notes, and online demos. That is enough to explain features, but it is not always enough to help people use a new tool in a real project.<\/p>\n<p>Local technical communities fill this gap. Builders can compare workflows, ask questions, and see how a tool behaves outside a prepared demo. The OpenAI Codex Ambassador Program supports people who create these learning environments.<\/p>\n<p>I am Vladislav Guzey, an OpenAI Codex Ambassador in Chiang Mai, Thailand. This article describes the program as a practical community system: its inputs, activities, expected outputs, and ways to prepare for a future cohort.<\/p>\n<blockquote>\n<p><strong>Information verified on August 1, 2026.<\/strong> Applications are currently paused. OpenAI says it intends to open a future cohort, but it has not published a date. Check the <a href=\"https:\/\/developers.openai.com\/community\/codex-ambassadors\" rel=\"noopener noreferrer nofollow\">official program page<\/a> for current information.<\/p>\n<\/blockquote>\n<h3>Program model<\/h3>\n<p>The Codex Ambassador Program connects OpenAI with local and specialist developer communities.<\/p>\n<p>Its participants may include:<\/p>\n<ul>\n<li>\n<p>Community and meetup organizers<\/p>\n<\/li>\n<li>\n<p>Open-source maintainers<\/p>\n<\/li>\n<li>\n<p>Student developer leaders<\/p>\n<\/li>\n<li>\n<p>Technical workshop facilitators<\/p>\n<\/li>\n<li>\n<p>Experienced Codex users who teach others<\/p>\n<\/li>\n<\/ul>\n<p>The model can be represented as a feedback system:<\/p>\n<pre><code>Codex team    \u2502    \u2502 resources and collaboration    \u25bcAmbassadors \u2500\u2500\u2500\u2500\u2500\u2500\u25ba events, guides, projects    \u25b2                         \u2502    \u2502                         \u25bc    \u2514\u2500\u2500\u2500\u2500 feedback \u2500\u2500\u2500\u2500\u2500 developers and communities<\/code><div class=\"code-explainer\"><a href=\"https:\/\/sourcecraft.dev\/\" class=\"tm-button code-explainer__link\" style=\"visibility: hidden;\"><img style=\"width:87px;height:14px;object-fit:cover;object-position:left;\"\/><\/a><\/div><\/pre>\n<p>The ambassador does not only distribute information. The ambassador also collects practical feedback and returns it to the team.<\/p>\n<h3>Four types of ambassador work<\/h3>\n<h4>1. Local events<\/h4>\n<p>Ambassadors can organize workshops, meetups, hackathons, build days, and similar sessions.<\/p>\n<p>For technical audiences, an event becomes more useful when participants can inspect a real repository and complete a task. A practical session might include:<\/p>\n<ol>\n<li>\n<p>A short explanation of the problem<\/p>\n<\/li>\n<li>\n<p>A demonstrated Codex workflow<\/p>\n<\/li>\n<li>\n<p>Independent or group implementation<\/p>\n<\/li>\n<li>\n<p>Review of the resulting changes<\/p>\n<\/li>\n<li>\n<p>Discussion of errors and limitations<\/p>\n<\/li>\n<\/ol>\n<p>The size of the event is not the main metric. A small workshop can produce better learning outcomes than a large presentation if participants have enough time to experiment.<\/p>\n<p>Current community events are listed in the <a href=\"https:\/\/developers.openai.com\/community\/meetups\" rel=\"noopener noreferrer nofollow\">Codex Meetups directory<\/a>.<\/p>\n<h4>2. Reusable technical materials<\/h4>\n<p>The program values resources that continue to help builders after an event. These may include:<\/p>\n<ul>\n<li>\n<p>Installation and beginner guides<\/p>\n<\/li>\n<li>\n<p>Repository-based tutorials<\/p>\n<\/li>\n<li>\n<p>Videos and recorded demonstrations<\/p>\n<\/li>\n<li>\n<p>Workshop plans and slide decks<\/p>\n<\/li>\n<li>\n<p>Open-source tools<\/p>\n<\/li>\n<li>\n<p>Codex skills and agents<\/p>\n<\/li>\n<li>\n<p>Tested prompt patterns<\/p>\n<\/li>\n<li>\n<p>Event reports with lessons learned<\/p>\n<\/li>\n<\/ul>\n<p>The best resource has a defined audience, a clear result, and enough detail to reproduce the workflow.<\/p>\n<p>For example, \u201cUsing coding agents\u201d is a broad topic. \u201cUsing Codex to understand an unfamiliar TypeScript repository and prepare a safe first patch\u201d is a reproducible learning objective.<\/p>\n<h4>3. Community development<\/h4>\n<p>Different groups require different content.<\/p>\n<div>\n<div class=\"table\">\n<table>\n<tbody>\n<tr>\n<th>\n<p align=\"left\">Audience<\/p>\n<\/th>\n<th>\n<p align=\"left\">Likely need<\/p>\n<\/th>\n<th>\n<p align=\"left\">Useful format<\/p>\n<\/th>\n<\/tr>\n<tr>\n<td>\n<p align=\"left\">Students<\/p>\n<\/td>\n<td>\n<p align=\"left\">Basic concepts and safe experimentation<\/p>\n<\/td>\n<td>\n<p align=\"left\">Guided beginner lab<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p align=\"left\">Professional developers<\/p>\n<\/td>\n<td>\n<p align=\"left\">Repository workflows and verification<\/p>\n<\/td>\n<td>\n<p align=\"left\">Hands-on engineering workshop<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p align=\"left\">Open-source maintainers<\/p>\n<\/td>\n<td>\n<p align=\"left\">Issue triage and contributor support<\/p>\n<\/td>\n<td>\n<p align=\"left\">Maintainer roundtable<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p align=\"left\">Founders<\/p>\n<\/td>\n<td>\n<p align=\"left\">Fast prototyping and product validation<\/p>\n<\/td>\n<td>\n<p align=\"left\">Build day<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p align=\"left\">Content creators<\/p>\n<\/td>\n<td>\n<p align=\"left\">Accurate demonstrations and examples<\/p>\n<\/td>\n<td>\n<p align=\"left\">Demo and feedback session<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n<p>An ambassador should understand the local audience before selecting a format.<\/p>\n<h4>4. Product and community feedback<\/h4>\n<p>Real-world feedback is another output of the program.<\/p>\n<p>Useful feedback may describe:<\/p>\n<ul>\n<li>\n<p>Where installation or onboarding fails<\/p>\n<\/li>\n<li>\n<p>Which instructions users misunderstand<\/p>\n<\/li>\n<li>\n<p>Workflows developers repeat<\/p>\n<\/li>\n<li>\n<p>Features that save time<\/p>\n<\/li>\n<li>\n<p>Questions that appear in multiple sessions<\/p>\n<\/li>\n<li>\n<p>Differences between beginner and advanced usage<\/p>\n<\/li>\n<\/ul>\n<p>Feedback becomes more useful when it includes context. The operating system, repository type, experience level, attempted workflow, and observed result can matter.<\/p>\n<h3>Program support and commitment<\/h3>\n<p>OpenAI currently lists several forms of support:<\/p>\n<ul>\n<li>\n<p>Codex and API credits for ambassador activities and events<\/p>\n<\/li>\n<li>\n<p>Starter kits that can be adapted<\/p>\n<\/li>\n<li>\n<p>Collaboration with ambassadors and the Codex team<\/p>\n<\/li>\n<li>\n<p>Invitations to selected future events<\/p>\n<\/li>\n<li>\n<p>Exclusive swag<\/p>\n<\/li>\n<\/ul>\n<p>These details may be different in a future cohort. Applicants should verify them when applications reopen.<\/p>\n<p>The current time expectation is approximately <strong>two to four hours per week<\/strong>, with at least <strong>one contribution per month<\/strong>.<\/p>\n<p>This should be treated as an ongoing responsibility. A single event may require planning, communication, venue preparation, technical testing, delivery, and follow-up. A guide or open-source project has a different workload, but it still needs maintenance and answers to user questions.<\/p>\n<h3>Application profile<\/h3>\n<p>OpenAI describes the program as relevant to people who already have hands-on experience building or supporting developer communities.<\/p>\n<p>A strong profile may include evidence such as:<\/p>\n<ul>\n<li>\n<p>A meetup or study group you helped organize<\/p>\n<\/li>\n<li>\n<p>An open-source repository you maintain<\/p>\n<\/li>\n<li>\n<p>Technical articles or videos<\/p>\n<\/li>\n<li>\n<p>Workshop materials<\/p>\n<\/li>\n<li>\n<p>Answers and support provided in a developer community<\/p>\n<\/li>\n<li>\n<p>Examples of real Codex workflows<\/p>\n<\/li>\n<\/ul>\n<p>This does not mean every applicant needs all of these items. A small number of useful, verifiable contributions can show more than a long list of unrelated activities.<\/p>\n<p>OpenAI has not published a permanent acceptance rate, fixed review time, or guaranteed cohort size. A future application form may also differ from earlier forms.<\/p>\n<h3>A practical preparation backlog<\/h3>\n<p>The following backlog is my advice, not an official application checklist.<\/p>\n<h4>Task 1: Document three real Codex workflows<\/h4>\n<p>For each workflow, record:<\/p>\n<pre><code class=\"yaml\">problem: What needed to be solved?context: Which repository, language, or environment was involved?codex_usage: What did Codex do?verification: How was the result checked?lesson: What should another developer know?<\/code><div class=\"code-explainer\"><a href=\"https:\/\/sourcecraft.dev\/\" class=\"tm-button code-explainer__link\" style=\"visibility: hidden;\"><img style=\"width:14px;height:14px;object-fit:cover;object-position:left;\"\/><\/a><\/div><\/pre>\n<p>Verification is important. A useful coding-agent example should explain how the output was reviewed or tested.<\/p>\n<h4>Task 2: Publish one focused resource<\/h4>\n<p>Select one repeated problem and explain it in simple steps. Include requirements, expected output, limitations, and troubleshooting notes.<\/p>\n<h4>Task 3: Run one small session<\/h4>\n<p>Invite a local group, student club, open-source community, or colleagues. Keep the first session focused. Collect the questions people ask and turn them into improvements for the next version.<\/p>\n<h4>Task 4: Define a measurable contribution<\/h4>\n<p>Instead of \u201cgrow the community,\u201d define an outcome:<\/p>\n<ul>\n<li>\n<p>Run a 90-minute workshop for 20 local developers<\/p>\n<\/li>\n<li>\n<p>Publish one tested workflow each month<\/p>\n<\/li>\n<li>\n<p>Create a starter repository for students<\/p>\n<\/li>\n<li>\n<p>Organize a maintainer discussion and publish the findings<\/p>\n<\/li>\n<\/ul>\n<p>The outcome should be small enough to deliver and useful enough to repeat.<\/p>\n<h3>Event example: OpenAI Build Week Chiang Mai<\/h3>\n<p>On July 18, 2026, I hosted an OpenAI Build Week community meetup in Chiang Mai. The audience included developers, founders, students, and AI-curious creators.<\/p>\n<p>We explored Codex through several surfaces, including the app, CLI, IDE, and cloud. The mixed audience created a useful test: a single session had to give beginners enough context while still providing practical value for experienced developers.<\/p>\n<figure class=\"\"><img decoding=\"async\" src=\"https:\/\/habrastorage.org\/r\/w1560\/getpro\/habr\/\/post_images\/584\/4fe\/ffa\/5844feffadccc6628b8b0f5c5cf7a2c2.jpg\" alt=\"Developers working during the OpenAI Build Week session in Chiang Mai\" sizes=\"(max-width: 780px) 100vw, 50vw\" srcset=\"https:\/\/habrastorage.org\/r\/w780\/getpro\/habr\/\/post_images\/584\/4fe\/ffa\/5844feffadccc6628b8b0f5c5cf7a2c2.jpg 780w,&#10;       https:\/\/habrastorage.org\/r\/w1560\/getpro\/habr\/\/post_images\/584\/4fe\/ffa\/5844feffadccc6628b8b0f5c5cf7a2c2.jpg 781w\" loading=\"lazy\" decode=\"async\"\/><\/p>\n<div><figcaption>Developers working during the OpenAI Build Week session in Chiang Mai<\/figcaption><\/div>\n<\/figure>\n<p>The strongest part was peer learning. Participants compared approaches and helped one another. This made the event more than a one-direction presentation.<\/p>\n<p>For developers in Thailand, I publish upcoming events, recaps, and Codex learning resources on <a href=\"https:\/\/proflead.dev\/codex\/\" rel=\"noopener noreferrer nofollow\">proflead.dev\/codex<\/a>. My listing is also available in the <a href=\"https:\/\/developers.openai.com\/community\/codex-ambassadors?ambassador=vladislav-viktorovich-guzey\" rel=\"noopener noreferrer nofollow\">official OpenAI Ambassador directory<\/a>.<\/p>\n<h3>Common questions<\/h3>\n<h4>Must an applicant already organize large events?<\/h4>\n<p>No. Relevant community experience is useful, but the activity does not need to be a conference. Workshops, open-source work, teaching, and smaller developer groups can be meaningful.<\/p>\n<h4>Can multiple ambassadors be based in one city?<\/h4>\n<p>Yes. The program focuses on community support rather than exclusive geographic ownership.<\/p>\n<h4>Is a computer science degree required?<\/h4>\n<p>OpenAI does not list a specific degree, job title, or number of professional coding years. Practical experience with Codex and an ability to support builders are more important.<\/p>\n<h4>When will the next cohort open?<\/h4>\n<p>No date has been announced. Use the official program page for updates.<\/p>\n<h3>Links<\/h3>\n<ul>\n<li>\n<p><a href=\"https:\/\/developers.openai.com\/community\/codex-ambassadors\" rel=\"noopener noreferrer nofollow\">Codex Ambassadors program and directory<\/a><\/p>\n<\/li>\n<li>\n<p><a href=\"https:\/\/developers.openai.com\/community\/meetups\" rel=\"noopener noreferrer nofollow\">Codex Meetups<\/a><\/p>\n<\/li>\n<li>\n<p><a href=\"https:\/\/developers.openai.com\/community\" rel=\"noopener noreferrer nofollow\">OpenAI developer community<\/a><\/p>\n<\/li>\n<li>\n<p><a href=\"https:\/\/github.com\/proflead\/codex-skills-library\" rel=\"noopener noreferrer nofollow\">My Codex Skills Library<\/a><\/p>\n<\/li>\n<li>\n<p><a href=\"https:\/\/github.com\/proflead\/codex-agents-library\" rel=\"noopener noreferrer nofollow\">My Codex Agents Library<\/a><\/p>\n<\/li>\n<li>\n<p><a href=\"https:\/\/proflead.dev\/codex\/\" rel=\"noopener noreferrer nofollow\">Codex events and resources in Thailand<\/a><\/p>\n<\/li>\n<\/ul>\n<p>The application period is only one stage of the process. The more important work is continuous: understand a developer\u2019s problem, create a useful activity or resource, verify that it helps, and improve it using feedback.<\/p>\n<\/div>\n<p>\u0441\u0441\u044b\u043b\u043a\u0430 \u043d\u0430 \u043e\u0440\u0438\u0433\u0438\u043d\u0430\u043b \u0441\u0442\u0430\u0442\u044c\u0438 <a href=\"https:\/\/habr.com\/ru\/articles\/1065632\/\">https:\/\/habr.com\/ru\/articles\/1065632\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Developer tools are often introduced through documentation, release notes, and online demos. That is enough to explain features, but it is not always enough to help people use a new tool in a real project.Local technical communities fill this gap. Builders can compare workflows, ask questions, and see how a tool behaves outside a prepared demo. The OpenAI Codex Ambassador Program supports people who create these learning environments.I am Vladislav Guzey, an OpenAI Codex Ambassador in Chiang Mai, Thailand. This article describes the program as a practical community system: its inputs, activities, expected outputs, and ways to prepare for a future cohort.Information verified on August 1, 2026. Applications are currently paused. OpenAI says it intends to open a future cohort, but it has not published a date. Check the official program page for current information.Program modelThe Codex Ambassador Program connects OpenAI with local and specialist developer communities.Its participants may include:Community and meetup organizersOpen-source maintainersStudent developer leadersTechnical workshop facilitatorsExperienced Codex users who teach othersThe model can be represented as a feedback system:Codex team    \u2502    \u2502 resources and collaboration    \u25bcAmbassadors \u2500\u2500\u2500\u2500\u2500\u2500\u25ba events, guides, projects    \u25b2                         \u2502    \u2502                         \u25bc    \u2514\u2500\u2500\u2500\u2500 feedback \u2500\u2500\u2500\u2500\u2500 developers and communitiesThe ambassador does not only distribute information. The ambassador also collects practical feedback and returns it to the team.Four types of ambassador work1. Local eventsAmbassadors can organize workshops, meetups, hackathons, build days, and similar sessions.For technical audiences, an event becomes more useful when participants can inspect a real repository and complete a task. A practical session might include:A short explanation of the problemA demonstrated Codex workflowIndependent or group implementationReview of the resulting changesDiscussion of errors and limitationsThe size of the event is not the main metric. A small workshop can produce better learning outcomes than a large presentation if participants have enough time to experiment.Current community events are listed in the Codex Meetups directory.2. Reusable technical materialsThe program values resources that continue to help builders after an event. These may include:Installation and beginner guidesRepository-based tutorialsVideos and recorded demonstrationsWorkshop plans and slide decksOpen-source toolsCodex skills and agentsTested prompt patternsEvent reports with lessons learnedThe best resource has a defined audience, a clear result, and enough detail to reproduce the workflow.For example, \u201cUsing coding agents\u201d is a broad topic. \u201cUsing Codex to understand an unfamiliar TypeScript repository and prepare a safe first patch\u201d is a reproducible learning objective.3. Community developmentDifferent groups require different content.AudienceLikely needUseful formatStudentsBasic concepts and safe experimentationGuided beginner labProfessional developersRepository workflows and verificationHands-on engineering workshopOpen-source maintainersIssue triage and contributor supportMaintainer roundtableFoundersFast prototyping and product validationBuild dayContent creatorsAccurate demonstrations and examplesDemo and feedback sessionAn ambassador should understand the local audience before selecting a format.4. Product and community feedbackReal-world feedback is another output of the program.Useful feedback may describe:Where installation or onboarding failsWhich instructions users misunderstandWorkflows developers repeatFeatures that save timeQuestions that appear in multiple sessionsDifferences between beginner and advanced usageFeedback becomes more useful when it includes context. The operating system, repository type, experience level, attempted workflow, and observed result can matter.Program support and commitmentOpenAI currently lists several forms of support:Codex and API credits for ambassador activities and eventsStarter kits that can be adaptedCollaboration with ambassadors and the Codex teamInvitations to selected future eventsExclusive swagThese details may be different in a future cohort. Applicants should verify them when applications reopen.The current time expectation is approximately two to four hours per week, with at least one contribution per month.This should be treated as an ongoing responsibility. A single event may require planning, communication, venue preparation, technical testing, delivery, and follow-up. A guide or open-source project has a different workload, but it still needs maintenance and answers to user questions.Application profileOpenAI describes the program as relevant to people who already have hands-on experience building or supporting developer communities.A strong profile may include evidence such as:A meetup or study group you helped organizeAn open-source repository you maintainTechnical articles or videosWorkshop materialsAnswers and support provided in a developer communityExamples of real Codex workflowsThis does not mean every applicant needs all of these items. A small number of useful, verifiable contributions can show more than a long list of unrelated activities.OpenAI has not published a permanent acceptance rate, fixed review time, or guaranteed cohort size. A future application form may also differ from earlier forms.A practical preparation backlogThe following backlog is my advice, not an official application checklist.Task 1: Document three real Codex workflowsFor each workflow, record:problem: What needed to be solved?context: Which repository, language, or environment was involved?codex_usage: What did Codex do?verification: How was the result checked?lesson: What should another developer know?Verification is important. A useful coding-agent example should explain how the output was reviewed or tested.Task 2: Publish one focused resourceSelect one repeated problem and explain it in simple steps. Include requirements, expected output, limitations, and troubleshooting notes.Task 3: Run one small sessionInvite a local group, student club, open-source community, or colleagues. Keep the first session focused. Collect the questions people ask and turn them into improvements for the next version.Task 4: Define a measurable contributionInstead of \u201cgrow the community,\u201d define an outcome:Run a 90-minute workshop for 20 local developersPublish one tested workflow each monthCreate a starter repository for studentsOrganize a maintainer discussion and publish the findingsThe outcome should be small enough to deliver and useful enough to repeat.Event example: OpenAI Build Week Chiang MaiOn July 18, 2026, I hosted an OpenAI Build Week community meetup in Chiang Mai. The audience included developers, founders, students, and AI-curious creators.We explored Codex through several surfaces, including the app, CLI, IDE, and cloud. The mixed audience created a useful test: a single session had to give beginners enough context while still providing practical value for experienced developers.Developers working during the OpenAI Build Week session in Chiang MaiThe strongest part was peer learning. Participants compared approaches and helped one another. This made the event more than a one-direction presentation.For developers in Thailand, I publish upcoming events, recaps, and Codex learning resources on proflead.dev\/codex. My listing is also available in the official OpenAI Ambassador directory.Common questionsMust an applicant already organize large events?No. Relevant community experience is useful, but the activity does not need to be a conference. Workshops, open-source work, teaching, and smaller developer groups can be meaningful.Can multiple ambassadors be based in one city?Yes. The program focuses on community support rather than exclusive geographic ownership.Is a computer science degree required?OpenAI does not list a specific degree, job title, or number of professional coding years. Practical experience with Codex and an ability to support builders are more important.When will the next cohort open?No date has been announced. Use the official program page for updates.LinksCodex Ambassadors program and directoryCodex MeetupsOpenAI developer communityMy Codex Skills LibraryMy Codex Agents LibraryCodex events and resources in ThailandThe application period is only one stage of the process. The more important work is continuous: understand a developer\u2019s problem, create a useful activity or resource, verify that it helps, and improve it using feedback.\u0441\u0441\u044b\u043b\u043a\u0430 \u043d\u0430 \u043e\u0440\u0438\u0433\u0438\u043d\u0430\u043b \u0441\u0442\u0430\u0442\u044c\u0438 https:\/\/habr.com\/ru\/articles\/1065632\/<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-489416","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/489416","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=489416"}],"version-history":[{"count":0,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/489416\/revisions"}],"wp:attachment":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=489416"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=489416"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=489416"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}