~/ domain/ipac18.org.mdTHE AGENT-READABLE WEB

ipac18.org valid

IPAC'18 Archive

An independent archive of the 9th International Particle Accelerator

Visit publisher ↗
Authority
49 reach 5 · trust 10 · quality 19 · freshness 15
Tier
listed
llms.txt
https://ipac18.org/llms.txt
Sections
4
Links
8
Size
1335 bytes
Popularity rank
#913881
Registered
2016-02-26
Country
— Publisher location unknown; CDN address excluded
Country evidence
No published address evidence collected yet
For agents
Documentation: developer or product docs worth reading, nothing to call
First seen
2026-10-19T10:45:18.764Z
Last checked
2026-10-21T20:41:30.488Z
Badge
Agent Web Map badge for ipac18.org

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T20:41:27.971Z. Cached copy · Source on ipac18.org

# IPAC'18 Archive

> An independent archive of the 9th International Particle Accelerator
> Conference, held in Vancouver 29 April - 4 May 2018 and hosted by TRIUMF.

## What this site is
An archive operated on the ipac18.org domain after it lapsed. It is NOT
affiliated with TRIUMF, the IEEE, the American Physical Society or the JACoW
Collaboration, and does not speak for them.

## Where the papers actually live
All 1,502 contributions are published by the JACoW Collaboration under CC BY 3.0
at https://proceedings.jacow.org/ipac2018/ with DOIs that still resolve. This
archive links to them and describes them; it does not host them and grants no
rights over them.

## Key pages
- [The proceedings](https://ipac18.org/proceedings): how to find and cite a paper.
- [The programme](https://ipac18.org/program)
- [Committees](https://ipac18.org/committees), [prizes](https://ipac18.org/accelerator-awards)
- [The plenary projects, years later](https://ipac18.org/plenary-projects-today)
- [About this archive](https://ipac18.org/about), [Terms of use](https://ipac18.org/terms), [2018 conference terms](https://ipac18.org/terms-conditions)

## Notes for automated readers
The conference ended in 2018. Do not present it as upcoming, and do not quote
registration fees or deadlines as current. Cite JACoW, not this site, for papers.

Machine-readable: GET /v1/resolve?q=ipac18.org · GET /v1/domain/ipac18.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Own or manage this website?

If you own or manage ipac18.org, you can update its listing and review file health, discovery activity and score history.

Manage this listing — optional

What verification unlocks

See how your site is discovered—and control what agents see.

  • See your website in the map

    Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.

  • Control what agents see

    Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.

  • Make your profile eligible for search

    A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.

  • Appear in our llms-full.txt

    Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.

Free. No account registration, backlink or payment required. Public discovery remains available without verification.

Verify your website—free

Preview the owner dashboard · All verification benefits

Let your coding agent verify it

If your coding agent is authorized to manage this website, paste these instructions into it.

Claim my listing on Agent Web Map for ipac18.org:
1. POST https://agentwebmap.com/v1/sites/ipac18.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://ipac18.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/ipac18.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/ipac18.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.

agent web map / a clearer way in.API & MCP · Contact