Tyrae Nikai Paul

Introduction

Tyrae Nikai Paul, the founder of CrofAI (crof.ai), a low-price LLM inference service, became the subject of a detailed technical exposé on September 13, 2026, when developer KTibow published “CrofAI is an OpenRouter wrapper,” arguing that the service silently routes many of its advertised models to the cheaper OpenRouter platform instead of the GPUs CrofAI claims to run. The post, backed by three independently re-runnable attestation runs published on GitHub, says CrofAI’s low prices are the product of that misrouting rather than of its own infrastructure. Paul — identified in the account as the owner who answers as “CROF_OWNER” in CrofAI’s public chat and confirmed by a state record as the sole member and registered agent of Nahcrof LLC — has disputed the latest findings.

Background Information

Nahcrof LLC, the company behind CrofAI, was formed on November 6, 2025, in Missouri, and is listed as active; Paul is its sole member and registered agent. The company also operates under the nahcrof.com domain and runs a beta instance at 67.nahcrof.com that appears in the blog’s chat records. CrofAI marketed itself as an independent inference provider with a large open-weight catalog — including DeepSeek V4 Pro, Kimi K3, GLM 5.x, Qwen, and the “greg” series — plus dedicated instances priced at roughly $0.0096–$0.0112 per GiB-hour of VRAM. In May 2026 it publicly attributed the end of its subscription offering to daily infrastructure costs above $1,000 against revenue between $500 and $1,000.

The Controversy or Incident That Led to Their Cancellation

Allegations. The claims in this section come from a September 13, 2026 technical blog post by KTibow (kendell.dev) and the attestation runs it links on GitHub. In the company chat, the owner concedes that some models (the greg series, qwen3.5-9b, and two misconfigured fallbacks) route through OpenRouter, but denies the rest and calls the latest attestation “entirely false.” Nothing has been charged or adjudicated. The blog’s author states they are “stopping use of CrofAI” and that they “don’t condone targeting CrofAI’s owner as a person.”

The blog’s central finding is that CrofAI accepts OpenRouter’s openrouter:advisor tool — unexpected for a self-hosting provider — and that the tool’s output across every model shows most of CrofAI’s catalog being served by a small handful of cheaper or weaker models: numerous DeepSeek, Qwen, and GLM entries routed to DeepSeek V4 Flash 0731; Kimi K3 and others to GLM 5.3 Flash; the entire greg series to Kimi K2.7 Code; and more. The author published three attestations on GitHub — before CrofAI’s first fix, after it, and after its last deploy — all on the same commit, and says the most common advisor result is identical in all three.

The account then walks through five fix attempts in CrofAI’s public chat. In shot 1, KTibow reports “falling back” behavior; the owner says OpenRouter is only an “all hell breaks loose fallback.” In shot 2, the owner concedes “a not insignificant amount of traffic” was going to OpenRouter, blames a misconfigured GPU router, and pushes an update. In shot 3, the owner states “I can assure you no requests are going to openrouter,” but the next morning’s attestation still shows OpenRouter fingerprints. In shot 4, the owner time-locks an explanation, disables “all fallbacks,” and deploys a “separate version” — yet the attestation taken thirty minutes later shows models still downloading images as OpenRouter clients and returning OpenRouter-generated response IDs; the model the owner said runs on a “local DGX Spark” was answered by a Qwen model, and its real weights (167 GB) could not fit the Spark (128 GB) in the first place. In shot 5, after the owner declared “a literal zero percent chance this somehow routes to openrouter” for every model except three he listed, the next-minute attestation shows crof.ai unchanged and outside providers seeing tokens only the beta domain should have served; the owner then admits the greg models “point to openrouter.”

The post closes with a cost argument: at CrofAI’s own dedicated-instance VRAM pricing, its advertised open-weight catalog implies roughly $2,170 per day of hardware (and a floor of $2,880 at Vast’s prices) — several times the $500–$1,000 daily revenue the company itself cited in May when killing its subscription tier — and several of the flagship models would need to be split across multiple machines with no NVLink between them, which CrofAI never claims or evidences doing. It is, the author writes, “implausible, not impossible.”

Public Reaction and Consequences

The reaction has so far been a one-on-one dispute rather than a public cancellation. The owner of CrofAI replied to the blog in the company chat, calling the latest audit “entirely false” while conceding the earlier ones were correct, and said “I’ll deploy it to the whole site just in case.” The blog author retested and found both crof.ai and 67.nahcrof.com still routing to OpenRouter, even after the owner’s “literal zero percent chance” assurance. The author’s disclosures state that they had previously promoted CrofAI and received unlimited tokens from it, sell tokens on a competitor, and that “nobody paid for this post”; they stopped using the service and recommended others do the same. No legal action, charge, or formal complaint is part of the record as of September 14, 2026.

Current Status

As of September 14, 2026, the public dispute is unresolved. CrofAI’s owner maintains that the deployed configuration contains no OpenRouter references except the models he listed; the blog’s latest attestation says the opposite is observable. Both crof.ai and nahcrof.com were returning HTTP 522 errors at the time of writing — the service intermittently unreachable — which complicates independent testing. The GitHub attestations remain live and re-runnable, and the post’s claim that the service is “an OpenRouter wrapper” stands as an allegation with public, checkable evidence rather than an adjudicated fact.

On September 14, 2026 — a day after the blog post — the owner wrote on X (@nahcrof) that, “In light of recent controversy and the mounting stress of running a company like nahcrof, I’m stepping away from this,” and announced that “You can no longer purchase credits on crof,” with a refund request page to follow as an alternative for existing balances. No statement specifically addressing the routing findings has been posted publicly.

Impact on Their Career and Life

The consequences so far are reputational and commercial rather than legal: a named founder whose company’s core product claim — self-hosted, low-priced inference — is publicly disputed with timestamped, re-runnable proof, a chat log in which the owner’s denials narrow over five “shots” into admissions, and a cost table showing the advertised fleet is several times the company’s own stated revenue. The blog author’s parting line frames the stakes: the owner is “just young and made a mistake.” Whether CrofAI’s customers treat the wrapper finding as a pricing explanation or a fraud is the open question the attestations were built to let them answer for themselves.