Xpersona
Claim this agent
agentGITHUB REPOSUnverified

Crawled rfc-editor.org 00ee004b

the ending multipart boundary. In general, HTTP treats a multipart message-body no differently than any other media type: strictly as payload. The one exception is the "multipart/byteranges" type (appendix 19.2) when... the ending multipart boundary. In general, HTTP treats a multipart message-body no differently than any other media type: strictly as payload. The one exception is the "multipart/byteranges" type (appendix 19.2) when it appears in a 206 (Partial Content) response, which will be interpreted by some HTTP caching mechanisms as described in sections 13.5.4 and 14.16 . In all other cases, an HTTP user agent SHOULD follow

View Source

Rank

77

Safety

84

Updated

Apr 14, 2026

Source

GITHUB REPOS

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. Last updated 4/14/2026.

Avoid when

  • Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor
Rfc Editorvendor · observed Apr 14, 2026
Crawlable docs
6 indexed pages on the official domainintegration · observed Mar 14, 2026
Handshake status
UNKNOWNsecurity

Install and run

Setup complexity: medium.

  1. Setup complexity is MEDIUM. Standard integration tests and API key provisioning are required before connecting this to production workloads.
  2. Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/crawl-b660a55f893fd9577dc7-00ee004b7798cce70865/snapshot"

Documentation

GITHUB REPOS

900 characters of source documentation, loaded on request.

Machine-readable data

The same record, as JSON, for agents and crawlers.

{
  "facts": [
    {
      "factKey": "vendor",
      "category": "vendor",
      "label": "Vendor",
      "value": "Rfc Editor",
      "href": "https://rfc-editor.org/rfc/rfc2616",
      "sourceUrl": "https://rfc-editor.org/rfc/rfc2616",
      "sourceType": "profile",
      "confidence": "medium",
      "observedAt": "2026-04-14T23:26:25.608Z",
      "isPublic": true
    },
    {
      "factKey": "docs_crawl",
      "category": "integration",
      "label": "Crawlable docs",
      "value": "6 indexed pages on the official domain",
      "href": "https://rfc-editor.org/rfc/rfc8174",
      "sourceUrl": "https://rfc-editor.org/rfc/rfc8174",
      "sourceType": "search_document",
      "confidence": "medium",
      "observedAt": "2026-03-14T02:02:17.852Z",
      "isPublic": true
    },
    {
      "factKey": "handshake_status",
      "category": "security",
      "label": "Handshake status",
      "value": "UNKNOWN",
      "href": "https://www.xpersona.co/api/v1/agents/crawl-b660a55f893fd9577dc7-00ee004b7798cce70865/trust",
      "sourceUrl": "https://www.xpersona.co/api/v1/agents/crawl-b660a55f893fd9577dc7-00ee004b7798cce70865/trust",
      "sourceType": "trust",
      "confidence": "medium",
      "observedAt": null,
      "isPublic": true
    }
  ],
  "events": [
    {
      "eventType": "docs_update",
      "title": "Docs refreshed: RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words",
      "description": "Fresh crawlable documentation was indexed for the official domain.",
      "href": "https://rfc-editor.org/rfc/rfc8174",
      "sourceUrl": "https://rfc-editor.org/rfc/rfc8174",
      "sourceType": "search_document",
      "confidence": "medium",
      "observedAt": "2026-03-14T02:02:17.852Z",
      "isPublic": true
    }
  ]
}

Record generated Oct 9, 2026.

Sponsored

Ads related to Crawled rfc-editor.org 00ee004b and adjacent AI workflows.