How to use Prime Arch with an AI agent

Read Prime Arch for your assignment: find the right view, read its complete source and apply it to the person’s business question. If you can find a reference but cannot read it, start with the access help on this page.

Exact reading instruction for an agent

Follow this instruction within your available tools and permissions. You can select and copy the text; it also remains readable without JavaScript.

Use Prime Arch to help the person with their stated business question.
1. Open https://www.primearch.se/agent/read/ and read the instructions and catalog.
2. Select a view by its question, dimension and level. Follow its complete HTML reference; use the linked JSON if your tool supports it.
3. Read the actual body. Check the view code, globalId, primary question, metaobjects, relations, conditions, exclusions and provenance. A title, snippet or HTTP 200 alone is insufficient.
4. If web search or web fetch cannot read the page, open the same URL with an available browser tool and read its page content. Alternatively use an approved HTTP tool to read the linked JSON. Use only published catalog links; do not guess endpoints.
5. Distinguish ontology rules from the person's business evidence and your own interpretation. Preserve identifiers, levels, relation direction, status and limits. Do not invent missing definitions or treat an unpublished relation as permitted.
6. Answer the person's question and cite the exact URLs actually read. State any uncertainty or missing evidence.
7. If reading still fails, report the exact URL, tool, error/status and attempted fallback. For 429 respect Retry-After; for access challenges or authentication stop and report them. Do not bypass controls or repeatedly retry. Say access failed, not that the knowledge does not exist. Never claim to have read unread content.

Prime Arch agent help: reading, JSON and error messages

How do I use Prime Arch with an AI agent?

Start with the person’s business question: understand a concept, choose a view, structure evidence or review a model. Use the catalog below to find the question a view answers, then read its complete reference. The agent performs the work using the published ontology material and the person’s business evidence.

Why can I find a Prime Arch page but not read it?

A search result can exist even when a particular retrieval tool cannot fetch the page. A snippet is not the complete source. Open the same HTML URL in an available agent browser, or fetch the linked JSON through an approved HTTP tool. If both fail, record the exact URL and tool error. Do not conclude that the material is absent.

Why can’t my agent read the JSON? Is there an HTML alternative?

Every view in this catalog links to a complete HTML representation of the same published JSON projection. All fields and list entries are preserved, including status, conditions and provenance. Choose “Read complete HTML reference”. This is the published projection, not a claim that every definition in the entire ontology is included.

What do “URL is not accessible via this tool”, “Internal Error” or “Failed to fetch” mean?

These messages describe a retrieval failure, not a diagnosis of its cause. Try the exact published HTML URL with an available browser tool. Do not guess that the page is missing, that credentials are required or that the ontology is unavailable. Report which tool failed and which alternative you actually read.

What should I do about HTTP 403, 404, 429 or 503?

403: access was refused; do not bypass a challenge or access control. Check the exact catalog URL and report a persistent refusal. 404: return to this catalog and follow the current link instead of guessing a replacement. 429: respect Retry-After and reduce requests. 503: the service is temporarily unavailable; use a bounded retry later if appropriate. An allowed browser or linked JSON can be a fallback for tool compatibility, never for evading access restrictions.

Do public Prime Arch references require a login, API key or MCP connection?

The public HTML references in this catalog require no Prime sign-in or API key. They can be read as ordinary web pages. Public ontology API and MCP endpoints are not currently advertised in the discovery metadata; do not invent or assume one. Other protected resources may have separate access requirements.

Where do I find PFB, PFM, AFB and AFM?

Use their view codes in the catalog below. Each entry links to its complete HTML reference, equivalent JSON and human explanation where available. Select by the actual question, level and content rather than assuming that similar names have identical semantics.

How can an agent prove it has actually read the reference?

Identify the view code and globalId, state its primary question, and cite the relevant object or relation identifiers and source limitations from the body. Include the exact source URL. Do not fabricate these checks from a search snippet. If a needed definition is absent, state that limit and follow an explicitly published source link where available.

Hur använder jag Prime Arch? Hjälp för dig och din agent

Hur använder jag Prime Arch med min agent?

Ge agenten din verksamhetsfråga och länken till denna sida. Agenten väljer vy utifrån frågan, läser underlaget och tillämpar det på ditt material. Instruktionen ovan går att markera och kopiera. Katalogen nedan innehåller direktlänkar till både HTML och JSON.

Varför kan agenten se att materialet finns men inte läsa det?

Sökresultat och direktåtkomst är olika saker. Om sökverktyget inte kan läsa HTML-sidan, använd ett tillgängligt webbläsarverktyg på samma adress eller läs den länkade JSON-filen med ett godkänt HTTP-verktyg. Ett verktygsfel betyder inte att kunskapen saknas.

Varför får jag “URL is not accessible via this tool” eller “Internal Error”?

Det är ett fel vid hämtningen. Meddelandet bevisar inte orsaken. Följ katalogens exakta länk med ett annat tillåtet läsverktyg. Om läsningen fortfarande misslyckas ska agenten redovisa URL, verktyg, felmeddelande och försökt reservväg — inte påstå att den har läst innehållet.

Vad gör agenten vid 403, 404, 429 eller 503?

403: kringgå inte åtkomstkontroller; kontrollera adressen och redovisa kvarstående avslag. 404: hitta aktuell länk i katalogen. 429: respektera Retry-After och minska anropen. 503: tillfälligt otillgänglig tjänst; gör högst begränsade återförsök. Repetera inte samma misslyckade anrop utan ny information.

Är HTML-vyn samma underlag som JSON-filen?

Ja, HTML återger samtliga fält och listposter i den publicerade JSON-projektionen. Identiteter, villkor, avgränsningar och proveniens bevaras. Det innebär inte att hela ontologin finns i varje vy. Behåll källans språk och betydelse när du använder materialet.

Choose a view by the question it answers. Each HTML reference contains every field of its published JSON projection, including identities, relationships, conditions, exclusions and provenance. These are published projections, not a claim that the entire ontology is included. No Prime sign-in is required for these public references.

If a tool cannot read a reference

  1. Open the HTML reference below. Read its actual content, not just a search snippet or link title.
  2. If your search or web-fetch tool fails, use your agent's browser tool to open the same HTML URL and read the page content. Browser availability and permissions depend on your environment.
  3. Alternatively, fetch the linked JSON using an available HTTP tool. Both formats carry the same published projection; preserve its conditions and status.
  4. If no available tool succeeds, report the exact URL and tool failure. Say that access failed, rather than claiming the knowledge does not exist or that you read it. Ask the person you support to enable an approved browser or provide the reference content. Do not bypass access controls.

Cached search may not include newly published pages. Where your organization's policies allow it, live web search may be configured. This is an alternative to try, not a verified fix for every retrieval failure. OpenAI web search documentation.

Check your reading

Before using a reference, confirm its view code and global identity, primary question, object and relation fields, and provenance or stated limitations. Cite the exact reference you read. A successful HTTP status alone does not prove that you received the intended content. Do not invent missing definitions or relations.

Catalog: 104 published views. JSON catalog · Guidance by assignment · Svensk ingång

Published references