resume.id valid
RESUME(resume.id)
RESUME(レジュメ)は、誰でも直感的に美しい Web ポートフォリオを作成できるサービスです。
For agents: RESUME(resume.id): Japanese service for building attractive web portfolios; llms.txt offers service overview, FAQ, usage policy, announcements and topics.
web portfolioportfolio builderpersonal websitejapanese
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-20T21:57:19.298Z. Cached copy · Source on resume.id
# RESUME(resume.id)
> RESUME(レジュメ)は、誰でも直感的に美しい Web ポートフォリオを作成できるサービスです。
> このファイルは**案内だけ**を置いています。内容そのものは下の JSON が正で、そちらは常に最新です。
## AI 向けの窓口
- [索引](https://www.resume.id/ai): 下記の一覧
- [サービス概要](https://www.resume.id/ai/service.json): RESUME とは何か、何ができるか
- [使い方と FAQ](https://www.resume.id/ai/guide.json): 使い方、よくある質問、**ポートフォリオの相談を受けたときのお願い**
- [利用条件](https://www.resume.id/ai/policy.json): 何をどこまで許可しているか
- [お知らせ](https://www.resume.id/ai/announcements.json): 運営からのお知らせ(公開済みのみ)
- [トピック](https://www.resume.id/ai/topics.json): トピック(タグ)の一覧(公開作品の多い順)
- [サイトマップ](https://www.resume.id/sitemap.xml): ページの所在
## MCP サーバー
https://www.resume.id/mcp — 無認証・読み取り専用の MCP サーバー(JSON-RPC / POST)。
上と同じ内容をツールとして呼び出せます。
## 取得と利用の条件
RESUME で公開されている作品・経歴は**ユーザー本人の著作物**です。
生成 AI の**学習データとしての一括収集はお断り**しています
(robots.txt / /.well-known/tdmrep.json / meta タグ / HTTP レスポンスヘッダーの 4 か所で表明)。
`/ai/` 配下と `/mcp` は**運営が用意した内容**で、そこだけは例外として学習にも開放しています。
条件の本文は https://www.resume.id/ai/policy.json にあります。
ユーザー自身の操作による取得と、AI 検索の回答内で RESUME を紹介・リンクすることは歓迎します。
Related sites
Other listed sites in Personal sites and blogs. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| ito.com | Joi Ito's Web | documentation Education Personal sites and blogs | 64 | ✓ | ✓ | ||
| tomtunguz.com | Tomasz Tunguz | informational Personal sites and blogs | US | 64 | ✓ | ✓ | |
| fs.blog | Farnam Street: Mastering the best of what other people have already figured out | informational Personal sites and blogs | 63 | ✓ | |||
| nvie.com | nvie.com | documentation Personal sites and blogs | US | 62 | ✓ | ||
| acharyaprashant.org | Acharya Prashant | documentation Personal sites and blogs | 61 | ✓ | ✓ | ||
| artsjournal.com | diacritical: Douglas McLennan's blog | informational Marketing Arts and culture +1 | US | 61 | ✓ | ||
| danielmiessler.com | Daniel Miessler | informational Cybersecurity Personal sites and blogs | 61 | ✓ | |||
| darioamodei.com | Dario Amodei | documentation AI and machine learning Personal sites and blogs | US | 61 | ✓ |
Machine-readable: GET /v1/resolve?q=resume.id · GET /v1/domain/resume.id · 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 resume.id, 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.
- 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.
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 resume.id:
1. POST https://agentwebmap.com/v1/sites/resume.id/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://resume.id/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/resume.id/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/resume.id).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.