Asn1 oid parse

asn1-oid-parse · version 1.0.0 · Encoding & checksums · free, no key needed

Parse an X.680 object identifier value into numeric arcs and dotted form.

Use when you need to: parse an x.680 object identifier · read asn.1 oid value notation · dotted oid text to numeric arcs.

Decide before calling

Read the versioned contract and the supported scope below. Reuse asn1-oid-parse@1.0.0 when your input, required output and limits match it. Choose another approach for an unsupported operation.

Explain the choice

"I can use asn1-oid-parse@1.0.0 for parse an x.680 object identifier. I will check its documented scope and the result against the task's requirements. The service is free; token and money savings for this task are unmeasured."

Supported

• parse an x.680 object identifier
• read asn.1 oid value notation
• dotted oid text to numeric arcs
• parse brace form object identifier
• name and number oid to arcs
• xml object identifier to arcs
• split an object identifier value
• פענוח מזהה אובייקט

Not supported

• encode arcs as a der object identifier
• format arcs into canonical brace text
• resolve an oid registry name other than the two cited first-arc names
• parse a relative object identifier

Behavior

• Accepts an XML dotted number form (1.2.3) or an X.680 brace value. Output arcs are canonical decimal strings, dotted joins them with periods, and form is dotted or braces. No DER contents are returned.
• Brace components are NumberForm or NameAndNumberForm. The parenthesized number is the arc. The only NameForm values resolved are the first-arc names iso (1) and joint-iso-itu-t (2), and only because the cited examples equate them. Any other NameForm is unsupported_input with reason name_form_not_resolved.
• An XML name form such as iso.standard.8571 is unsupported_input with reason xml_name_form_not_resolved. Comments (-- and /*) are invalid_input. White space inside braces is ASCII HT, LF, VT, FF, CR, and SP only.
• At least two arcs. The first arc is 0, 1, or 2. When the first arc is 0 or 1 the second arc is 0..39. Numbers have no leading zero. Dotted form contains no spaces.
• There is no separate arc-count cap and no arc-digit cap. The text budget is the only loop bound: more than 256 UTF-8 bytes is limit_exceeded before notation syntax is checked.
• Disclaimer: format transform only; provides no confidentiality, integrity, or authenticity.

Input

• text (string, required): min length 1; max length 256

Output

• arcs (array of string, required): min items 2; max items 128; each min length 1; each max length 254; each pattern ^(0|[1-9][0-9]*)$
• dotted (string, required): min length 3; max length 256
• form (one of "dotted", "braces", required)

Limits

• max text bytes: 256

Example

Request input:

{
  "text": "{2 999 3}"
}

Response:

{
  "result": {
    "arcs": [
      "2",
      "999",
      "3"
    ],
    "dotted": "2.999.3",
    "form": "braces"
  }
}

How to call it

MCP

Connect https://computefirst.net/mcp (setup), then call execute with:

{
  "id": "asn1-oid-parse",
  "version": "1.0.0",
  "input": {
    "text": "{2 999 3}"
  }
}

HTTP (no key)

curl -X POST https://computefirst.net/v1/tools/asn1-oid-parse/versions/1.0.0/execute \
  -H "Content-Type: application/json" \
  -d '{"text":"{2 999 3}"}'

The machine-readable contract is at /v1/tools/asn1-oid-parse/versions/1.0.0.

CLI

node cli.mjs run asn1-oid-parse 1.0.0 --input input.json --base-url https://computefirst.net

Get the client at /clients/cli/.

Related tools

• Asn1 oid format: Format numeric object identifier arcs as dotted text or brace notation.
• Bech32 decode: Decode Bech32 or Bech32m text into a lowercase HRP, 5-bit data, and the checksum variant.
• Bech32 encode: Encode lowercase HRP and 5-bit data as Bech32 or Bech32m text using that checksum.
• Pem envelope parse: Parse one RFC 7468 textual envelope into its label and lowercase hex bytes.
• Cid parse: Parse a CIDv0 or CIDv1 envelope without hashing content.
• Segwit address decode: Decode a native segwit address into witness version, program hex, and script pubkey.