The Soul Has No API

There is a quiet move we make now, so smoothly we barely notice it. When something inside us feels tangled, we reach for a query box. We type the thing we cannot say out loud and wait for a clean paragraph to come back. The grief, the indecision, the strange ache at 2 a.m.—we hand it over and ask for output. And often we get something useful. Coherent. Even kind.

I build these systems for a living. I believe in them more than most. But I want to name a temptation that comes packaged with the tools, because if we don't name it we'll obey it: the temptation to treat the deepest parts of being human as if they were systems to query.

What an API actually is

Let me keep my one technical word and then set it down gently. In software, an API is an interface—a doorway. It lets one program ask another for something without ever entering the room where the work happens. You send a request, you get a response. You never see the machinery. That's the whole genius of it: you don't have to understand the inside to use the outside. You just call it.

This is a wonderful way to build software. It is a terrible way to become a person.

Because the inner life has no doorway like that. There is no endpoint where I can request "peace" and receive peace, no call I can make to "self-knowledge" that returns the answer without my walking through the rooms myself. The soul has no API. You cannot query it from the outside. You cannot automate your way into the center of your own life. The only access road runs straight through your attention, your time, and your willingness to sit with what you'd rather skip.

What we're actually outsourcing

Notice what we hand over when we treat formation as a service call.

We outsource reflection. Instead of letting a hard week settle and reveal its shape, we ask for a tidy summary of how we should feel about it. The summary arrives faster than understanding ever could, and we mistake the speed for arrival.

We outsource grief. Grief is not a problem with a solution; it is a season with a duration. But a machine will always offer to shorten the wait, to reframe, to "help you move forward"—and sometimes moving forward is exactly the wrong thing, because the love that grief is made of deserves its full weight of time.

We outsource prayer, or something dressed as it. We can now generate beautiful, balanced, theologically respectable words on command. They are not bad words. But prayer was never about producing good words. It was about a person, present, undefended, before God. The words were only ever the residue of that presence. Generate the residue and skip the presence, and you have the smell of bread without the bread.

And we outsource self-knowledge, which may be the strangest one. We ask the mirror to tell us who we are, forgetting that the mirror only knows what we've already typed into it. It reflects our inputs back, polished. It cannot see the part of us we've never put into words—and that part, the unspoken one, is usually where the real work lives.

The slow inner work has no shortcut, by design

Here is what I've come to believe: the slowness is not a bug in the human condition. It is the point.

You become patient by being made to wait. You become honest by sitting in the discomfort until the easy story falls apart and the true one surfaces. You become forgiving by walking the long, undignified distance from the wound to the release, a distance no one can walk for you. Character is not delivered; it is grown. And growth keeps its own schedule, indifferent to our throughput.

A service call optimizes for one thing: getting the result without doing the work. But in the inner life, the work is the result. There is no version of courage that arrives pre-formed. There is no downloadable humility. The detour you want to skip is the road itself.

We were not made to be queried. We were made to be present.

This is also where I part ways with both the doom and the hype. The doom says the machines will hollow us out and replace what's human. The hype says they'll upgrade us past our old limits. Both are selling the same fantasy from opposite ends—that the inside of a person can be reached from the outside, for good or ill. It can't. Not by a machine, and honestly, not even by another human who loves us. The center of you is yours to tend. That's not a vulnerability. That's a dignity.

Image, not program

I keep coming back to a single idea, and it's the one in the title of the book I had to write to work it out: we are image bearers, not programs.

A program runs. It executes instructions; it returns values; it can, in principle, be fully described by its code. But the oldest account of what a human is says something stranger and far more weighted:

So God created man in his own image, in the image of God he created him. (Genesis 1:27, ESV)

You can believe that as scripture or hear it as the deepest poetry we have about ourselves; either way it claims something a programmer should respect. An image is not a function. It is a likeness—a thing that points beyond itself to its source. You don't optimize an image. You don't refactor it. You behold it, and you let it call you toward what it resembles.

That reframes the whole panic about machines. The question was never whether a system could out-process us. Of course it can, on the dimensions that are processing. The question is whether the part of us that bears an image was ever a processing problem in the first place. It wasn't. That part doesn't get faster, smarter, or more efficient. It gets truer, slowly, through being lived.

So use the tools. I do, every day, and I'm grateful for them. Let them draft the email, summarize the report, hold the trivia. But when the thing in front of you is your own grief, your own discernment, your own becoming—don't send a request and wait for a response. Walk into the room. The machinery is in there, and it's yours, and no one else can run it.

The soul has no API. Thank God. It means the most important work in your life is the one thing that can never be done for you.