King Solomon and the 72 Spirits [The Legend Behind Modern Protection and Entity Work]

Before Solomon was known as a master of spirits, he was a king with a construction problem. The Temple needed to be built, the labor was immense, and something was actively working against the effort — something that could not be solved with more workers or more stone.

What happened next became the foundation of an entire tradition of protective and command-based magic that is still practiced today — one I draw on directly in entity pact and protection work. The story is worth knowing in full, because the situation that started it is more familiar than you might expect.

The Problem That Started It All

According to the tradition, one of the master craftsmen working on the Temple had a son who was being tormented by something invisible. Each evening, a spirit came to him and drained his strength — taking half his wages, half his food, and reportedly half his actual life force, sucking the thumb of his right hand until the boy grew thin, weak, and increasingly unable to work.

The father brought the problem to Solomon. Not as a medical complaint — as a spiritual one. Something unseen was attaching itself to his son and feeding on him, and ordinary remedies had done nothing. Solomon, rather than dismissing it or offering vague comfort, treated it as exactly what it was: a real spiritual problem requiring a real spiritual solution. He prayed for the means to confront it directly.

The Spirit Ornias and the First Interrogation

The answer to Solomon's prayer arrived as a ring — engraved with a seal of immense authority, delivered by archangel Michael with instructions on exactly how to use it. Solomon gave the ring to the boy and told him precisely what to say to the spirit when it returned that evening.

When the spirit, named Ornias, came again to drain him, the boy threw the ring at its chest. The spirit cried out, begged for mercy, and — bound by the authority of the seal — was forced into submission. Solomon had it brought before him directly. And rather than destroy it or simply banish it, he questioned it.

This interrogation is the part of the story most people miss, and it's the most important part. Solomon didn't just neutralize one threat. He extracted information — what Ornias was, what it fed on, what weakened it, and crucially, what other spirits existed that operated the same way. Each answer led to the next spirit being identified, summoned, and bound in turn.

How It Became 72

Each spirit Solomon bound was made to give an account of itself — its name, the specific harm it caused, and which angel or force was capable of restraining it. Over the course of his reign, that catalogue grew until it numbered seventy-two distinct spirits, each with a defined nature: some caused illness, some caused discord between people, some caused confusion or deception, some drained wealth or vitality the way Ornias had.

This catalogue is what later became formalized into the grimoire tradition — most famously the Lesser Key of Solomon, with its section called the Ars Goetia, which lists each of the seventy-two by name and seal. Whatever you think of the historical authorship of these later texts, the principle they preserve is the same one established in the original story: spirits that cause harm are not random or unknowable. They have specific natures, specific weaknesses, and specific methods by which they can be identified and contained.

This is the entire foundation of structured entity pact work — not vague banishment, but precise identification followed by binding.

Why Confrontation, Not Avoidance

The instinct most people have when they sense something negative attached to them — bad luck that won't break, a heaviness that doesn't lift, a specific person whose presence seems to coincide with things going wrong — is to avoid, ignore, or simply hope it passes. Solomon's example is the opposite of that instinct, and the tradition holds that the opposite approach is the one that actually works.

A spirit or negative influence that is avoided continues operating exactly as it was. One that is identified, confronted directly through proper structure, and bound stops. The difference is not bravery for its own sake — it's that avoidance leaves the situation exactly as open as it was, while direct confrontation through the correct method closes it.

How This Principle Protects People Today

When a client comes to me describing something that sounds like Ornias and the boy's story without realizing the parallel — persistent exhaustion with no medical explanation, a specific person whose involvement in their life always seems to coincide with loss, a pattern of bad luck targeted enough that it stops feeling like coincidence — the approach draws directly on this tradition.

First, identification: what is actually attached, and what is its nature. Second, structured confrontation: not a vague cleansing, but a working built specifically to address what was identified. Third, binding or removal: ensuring the influence cannot simply return once the immediate work is done.

If what you're experiencing matches this pattern, a reading is the right first step — it identifies specifically what's attached and what kind of working it requires. From there, a protection or entity pact working applies the same structured approach Solomon used: name it, confront it, bind it.

Frequently Asked Questions

Final Thoughts

The story of Ornias and the boy is, at its heart, a story about a problem that ordinary remedies couldn't touch — and a method that worked precisely because it confronted the problem directly instead of hoping it would resolve on its own.

That principle hasn't aged. If something has been draining you in a way you can't fully explain, the path forward is the same one it always was.

 

READY TO TAKE THE NEXT STEP?

Every Casting Is Same-Day.

Every casting includes a free recast guarantee, no risk, no exceptions.

BROWSE LOVE SPELLS