GUID (Global Unique IDentifier)

Hi, we do not use a GUID, and instead use a 17-character alphanumeric strings (e.g., J8uR2KxPqL9nZ5t7m)

It would be easy for you to map this format on your side between the two formats using the code below on your system (bonus, its also UUIDv4):

const ALPHABET = "0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ";
// 1. Meteor ID -> Valid UUIDv4
function meteorIdToUuid(id) {
  // Convert Base62 Meteor ID to a BigInt (approx 101 bits of entropy)
  let num = 0n;
  for (const char of id) {
    num = num * 62n + BigInt(ALPHABET.indexOf(char));
  }
  // Convert BigInt to 32 hex characters (padded)
  let hex = num.toString(16).padStart(30, '0');
  // Insert UUIDv4 version '4' and variant '8' (bit-compliant)
  // UUIDv4: 8 chars - 4 chars - (4) + 3 chars - (8) + 3 chars - 12 chars
  const part1 = hex.slice(0, 8);   // 8
  const part2 = hex.slice(8, 12);  // 4
  const part3 = hex.slice(12, 15); // 3 (will follow the '4')
  const part4 = hex.slice(15, 18); // 3 (will follow the '8')
  const part5 = hex.slice(18, 30); // 12
  return `${part1}-${part2}-4${part3}-8${part4}-${part5}`;
}
// 2. Valid UUIDv4 -> Meteor ID
function guidToMeteorId(guid) {
  const clean = guid.replace(/-/g, '');
  // Extract only the original data bits (skip the fixed '4' at index 12 and '8' at index 16)
  const hex = clean.slice(0, 12) + clean.slice(13, 16) + clean.slice(17);
  // Convert hex back to BigInt
  let num = BigInt('0x' + hex);
  // Convert BigInt back to Base62 string
  let id = "";
  while (num > 0n) {
    id = ALPHABET[Number(num % 62n)] + id;
    num = num / 62n;
  }
  return id.padStart(17, ALPHABET[0]); // Ensure 17 chars
}
// --- Test ---
const originalId = "J8uR2KxPqL9nZ5t7m";
const validUuid = meteorIdToUuid(originalId);
const restoredId = guidToMeteorId(validUuid);
console.log("Original Meteor ID:", originalId);
console.log("Strict Valid UUIDv4:", validUuid); // Matches xxxxxxxx-xxxx-4xxx-8xxx-xxxxxxxxxxxx
console.log("Restored Meteor ID: ", restoredId); // J8uR2KxPqL9nZ5t7m

@Stephen,

Amazing, we will not be doing anything with this, more was curious to see if your foundation as setup to make a epic future with other tool integrations....sounds like its a yes.

Side note passing QTO from other tools is a low priority. There are higher priority "takeoff to estimate" integrations that we need once the API gets up and running, such as:

1. Make a project, then you can make estimates that go with takeoffs in one spot........why am I making projects in both tools LAME!
2. Passing back WBS's at the project and enterprise level
3. Using AI to help auto-select the line item the takeoff should be matched to the estimating database.
4. areas
5. units
6. Passing formulas to estimating
7. 
   
8. 
   
9. Quantity takeoff integration sits about here for reference.

@kyle you forgot "Profit" at the end